CVE-2026-29066: @tinacms/cli TinaCMS CLI Has Arbitrary File Vulnerability

MODERATE
Advisory Identifier: GHSA-m48g-4wr2-j2h6
CVSS 6.2
CWE-552 CWE-200
Published
Advisory Summary

CVE-2026-29066 is a MODERATE (CVSS 6.2) tinacms cli has arbitrary file vulnerability (CWE-552: Files or Directories Accessible to External Parties) affecting @tinacms/cli libraries in the npm ecosystem. The issue involves tinacms cli has arbitrary file read via disabled vite filesystem restriction. Remediation is available by upgrading affected packages to version 2.1.8.

CVE-2026-29066 at a Glance

CVE Identifier CVE-2026-29066
GHSA Identifier GHSA-m48g-4wr2-j2h6
Severity MODERATE
CVSS v3.1 Base Score 6.2
CWE Classification CWE-552: Files or Directories Accessible to External Parties
Affected Product @tinacms/cli
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 6.2

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-29066

To remediate this vulnerability, upgrade all affected @tinacms/cli dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@tinacms/cli fixed: 2.1.8
npm install @tinacms/cli@2.1.8
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @tinacms/cli

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-29066, inspect your project dependencies using npm:

npm ls @tinacms/cli

Analyze the terminal output to locate any version of @tinacms/cli in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.1.8), your application is affected.

Note: The npm ls @tinacms/cli command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-552: Files or Directories Accessible to External Parties, where the product makes files or directories accessible to unauthorized actors, even though they should not be. In @tinacms/cli, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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 ``` <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: - 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

CVE-2026-29066 Affected @tinacms/cli Versions

1 component(s)
Fixed Versions:
2.1.8
Product / Package Ecosystem Affected Versions Fixed Version
@tinacms/cli
npm
< 2.1.8
2.1.8

References

Frequently Asked Questions

What is CVE-2026-29066?
CVE-2026-29066 is a security vulnerability in @tinacms/cli involving TinaCMS CLI has Arbitrary File Read via Disabled Vite Filesystem Restriction under CWE-552: Files or Directories Accessible to External Parties.
Which @tinacms/cli versions are affected?
Affected versions include releases prior to 2.1.8 across affected packages: @tinacms/cli.
What version fixes CVE-2026-29066?
Upgrading to 2.1.8 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @tinacms/cli affected?
Yes, @tinacms/cli is affected in releases prior to 2.1.8. Upgrade your dependency to 2.1.8 or later.
What is the CVSS score of CVE-2026-29066?
CVE-2026-29066 has a CVSS v3.1 base score of 6.2 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-29066?
CVE-2026-29066 is classified under CWE-552: Files or Directories Accessible to External Parties (The product makes files or directories accessible to unauthorized actors, even though they should not be.).
How can I check npm dependencies for CVE-2026-29066?
Run the dependency tree command: 'npm ls @tinacms/cli'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-m48g-4wr2-j2h6",
  "modified" : "2026-03-12T20:32:43Z",
  "published" : "2026-03-12T20:32:43Z",
  "aliases" : [ "CVE-2026-29066" ],
  "summary" : "TinaCMS CLI has Arbitrary File Read via Disabled Vite Filesystem Restriction",
  "details" : "## Summary\nThe 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\n\n## Details\nWhen running `tinacms dev`, the CLI starts a Vite dev server configured in:\n`packages/@tinacms/cli/src/next/vite/index.ts`\n```\nserver: {\n  host: configManager.config?.build?.host ?? false,\n  ...\n  fs: {\n    strict: false, // Disables Vite's filesystem access restriction\n  },\n},\n```\nTinaCMS 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.\nAdditionally, the server enables permissive CORS (cors() with no origin restriction), which may further facilitate browser-based exploitation such as DNS rebinding attacks.\n\n## PoC\n\n**Prerequisites**: TinaCMS CLI dev server running (default port 4001).\n\n- Read system files directly:\n```\ncurl http://localhost:4001/etc/passwd\n```\n<img width=\"705\" height=\"332\" alt=\"image\" src=\"https://github.com/user-attachments/assets/6fd0e1c7-a549-40c8-bc81-af9c343f52a0\" />\n\n```\ncurl http://localhost:4001/etc/hostname\n```\n<img width=\"631\" height=\"41\" alt=\"image\" src=\"https://github.com/user-attachments/assets/bd103dc3-d4c3-4774-8007-b55de3fc2a9e\" />\nVite resolves and serves the absolute path directly from the filesystem.\n\n\n## Impact\nAny developer running tinacms dev in an environment where the dev server port is reachable by an attacker. This includes:\n\n- Cloud IDEs (GitHub Codespaces, Gitpod) where ports are automatically forwarded and publicly accessible\n\n- Docker or VM setups with port forwarding configured\n\n- Misconfigured environments binding to 0.0.0.0 via the build.host config option\n\n- Systems targeted via DNS rebinding attacks, leveraging the unrestricted CORS policy\n\n- Local environments with malicious dependencies running on the same machine\n\nAn attacker who can reach port 4001 can:\n\n- Read any file readable by the server process (/etc/passwd, /etc/shadow, SSH private keys)\n\n- Exfiltrate environment variables and secrets via /proc/self/environ\n\n- Access cloud credentials and API keys from configuration files",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@tinacms/cli"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.1.8"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/tinacms/tinacms/security/advisories/GHSA-m48g-4wr2-j2h6"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-29066"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/tinacms/tinacms"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200", "CWE-552" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-12T20:32:43Z",
    "nvd_published_at" : "2026-03-12T17:16:50Z"
  }
}