TinaCMS CLI (<= 2.7.0) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/tinacms-cli--2.7.0/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioFri, 09 Oct 2026 21:24:01 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgTinaCMS CLI Arbitrary Code Execution via Git Branch Name Injectionhttps://feed.craftedsignal.io/briefs/2026-10-tina-cli-code-injection/Fri, 09 Oct 2026 21:24:01 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-tina-cli-code-injection/The TinaCMS CLI package fails to sanitize Git branch names during client code generation, allowing an attacker to inject and execute arbitrary JavaScript expressions within consumer build environments.The TinaCMS CLI (up to version 2.7.0) contains a code injection vulnerability arising from the unsafe handling of Git branch names during the generation of client source code. The package reads environment variables like VERCEL_GIT_COMMIT_REF or GITHUB_BRANCH and incorporates the raw string into the generated client.ts file without any sanitization or encoding. Because the resulting string is placed inside a single-quoted JavaScript template, an attacker can use a Git branch name containing single quotes and JavaScript syntax to escape the string literal and execute arbitrary code. This execution occurs during the build process of consumer projects, such as preview deployments in CI/CD pipelines, granting the attacker access to build-time environment variables, credentials, and the ability to modify build artifacts.

Attack Chain

  1. Attacker identifies a target repository using an affected version of tinacms/cli for their build pipeline.
  2. Attacker initiates a pull request or creates a branch in the target repository.
  3. Attacker names the Git branch with a malicious payload (e.g., x'+(globalThis.__TINA_PROBE='hit')+').
  4. The victim's CI/CD platform (e.g., Vercel, GitHub Actions) triggers an automated build for the new branch.
  5. The TinaCMS CLI codegen process reads the malicious branch name from the environment.
  6. The CLI concatenates the payload into the client.ts template and writes it to the local file system.
  7. The CI build process runs a bundler (e.g., esbuild) which parses and evaluates the injected JavaScript code.
  8. The injected expression executes within the build environment, potentially leaking secrets or altering the final deployment artifact.

Impact

Successful exploitation results in arbitrary code execution within the build environment. This poses a significant risk to CI/CD pipelines by potentially exposing NPM_TOKEN, VERCEL_TOKEN, cloud API keys, and other build-time secrets. Furthermore, attackers can modify build artifacts to inject malicious code into the final production output, leading to downstream supply-chain compromises for users of the deployed application.

Recommendation

  1. Upgrade @tinacms/cli to a version that properly sanitizes branch input or migrates runtime configuration to JSON files as recommended by the vendor.
  2. Audit CI/CD logs for build-time errors occurring during the codegen phase, as malformed branch names may cause unexpected build failures.
  3. Review CI/CD environment configurations to minimize the exposure of sensitive tokens and secrets during preview deployments, which are most vulnerable to this attack vector.
  4. Patch CVE-2026-108259 immediately by updating the affected @tinacms/cli package in package.json.
]]>highadvisorysupply-chaincode-injectionci-cdrce