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 TinaCMS middleware only intercepts…
Published Mar 12, 2026
Affected packages
@tinacms/cli
- Ecosystem
- npm
- Affected
- < 2.1.8
- Fixed in
- 2.1.8
- Check
npm ls @tinacms/cli
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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).
- Read system files directly:
curl http://localhost:4001/etc/passwdcurl http://localhost:4001/etc/hostnameVite 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:
- Cloud IDEs (GitHub Codespaces, Gitpod) where ports are automatically forwarded and publicly accessible
- Docker or VM setups with port forwarding configured
- Misconfigured environments binding to 0.0.0.0 via the build.host config option
- Systems targeted via DNS rebinding attacks, leveraging the unrestricted CORS policy
- Local environments with malicious dependencies running on the same machine
An attacker who can reach port 4001 can:
- Read any file readable by the server process (/etc/passwd, /etc/shadow, SSH private keys)
- Exfiltrate environment variables and secrets via /proc/self/environ
- Access cloud credentials and API keys from configuration files
Credited to alaeddine03.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-108259
Tina: Code injection via unescaped Git branch name in generated client source
high8.2Oct 9, 2026CVE-2026-63123
Tina: Cross-origin `POST /media/upload/*` requests can write arbitrary files into the Tina dev server media root
medium6.5Aug 19, 2026CVE-2026-54074
@tinacms/cli: Remote Code Execution in @tinacms/cli via Forestry migration — unsanitised __TINA_INTERNAL__ marker in user-controlled YAML labels
high7.8Jun 19, 2026CVE-2026-28792
TinaCMS CLI Dev Server Vulnerable to Cross-Origin File Exfiltration via CORS Misconfiguration + Path Traversal in TinaCMS
critical9.6Mar 12, 2026CVE-2026-28793
TinaCMS Vulnerable to Path Traversal Leading to Arbitrary File Read, Write and Delete
high8.4Mar 12, 2026CVE-2025-68278
tinacms is vulnerable to arbitrary code execution
high7.3Dec 18, 2025
