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).
- Read system files directly:
curl http://localhost:4001/etc/passwd
curl http://localhost:4001/etc/hostname
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
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | @tinacms/cli | < 2.1.8 | 2.1.8 |
References
- CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N- Weakness (CWE)
CWE-200, CWE-552- Platform
- npm
- Package
@tinacms/cli- Disclosed
- 12.03.2026
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-m48g-4wr2-j2h6 - CC BY 4.0
Vulnerability history: @tinacms/cli
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 9
- First → latest
- 02.2023 10.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 1
- High 6
- Medium 2
Disclosures per year
- 2023: 1
- 2024: 1
- 2025: 1
- 2026: 6
-
TinaCMS CLI has Arbitrary File Read via Disabled Vite Filesystem Restriction this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.