@tinacms/cli
Affected
- introduced
0, fixed2.1.8(semver)
Fixed versions
2.1.8
Fix
- Fixed version
2.1.8npm install @tinacms/[email protected]
Advisory
Also known as: CVE-2026-29066
TinaCMS CLI has Arbitrary File Read via Disabled Vite Filesystem Restriction
Summary
The TinaCMS CLI dev server configures Vite with server.fs.strict: false, which disables Vite's built-in filesystem access restriction. This allows any unauthenticated attacker who can reach the dev server to read arbitrary files on the host system
Details
When running tinacms dev, the CLI starts a Vite dev server configured in:packages/@tinacms/cli/src/next/vite/index.ts
server: {
host: configManager.config?.build?.host ?? false,
...
fs: {
strict: false, // Disables Vite's filesystem access restriction
},
},
TinaCMS middleware only intercepts specific route prefixes (/media/*, /graphql, /altair, /searchIndex). Any request to a path outside these routes falls through to Vite's default static file handler, which will serve the file directly from the absolute path on the filesystem.
Additionally, the server enables permissive CORS (cors() with no origin restriction), which may further facilitate browser-based exploitation such as DNS rebinding attacks.
PoC
Prerequisites: TinaCMS CLI dev server running (default port 4001).
curl http://localhost:4001/etc/passwd
<img width="705" height="332" alt="image" src="https://github.com/user-attachments/assets/6fd0e1c7-a549-40c8-bc81-af9c343f52a0" />
curl http://localhost:4001/etc/hostname
<img width="631" height="41" alt="image" src="https://github.com/user-attachments/assets/bd103dc3-d4c3-4774-8007-b55de3fc2a9e" />
Vite resolves and serves the absolute path directly from the filesystem.
Impact
Any developer running tinacms dev in an environment where the dev server port is reachable by an attacker. This includes:
An attacker who can reach port 4001 can:
Medium Basis: The source's own band: MODERATE
0, fixed 2.1.8 (semver)2.1.8
2.1.8npm install @tinacms/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0