Tina: Code injection via unescaped Git branch name in generated client source
CVE-2026-108259GHSA-pwhx-cvv3-qj5c
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (@tinacms/cli 3.0.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm @tinacms/cli
- Affected
- <= 2.7.0
- Fixed in
- 3.0.0
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-pwhx-cvv3-qj5c lists affected ranges: npm @tinacms/cli >=0 <=2.7.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-pwhx-cvv3-qj5c lists affected ranges: npm @tinacms/cli >=0 <3.0.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 8.2 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
- EPSS
- CVE-2026-108259: 0.33% estimated exploitation activity in the next 30 days; percentile 26.41 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary @tinacms/cli inserts the raw Git branch value into the generated client.ts source without escaping or encoding. A Git-valid branch name can close the string literal and inject an arbitrary JavaScript expression that executes when the consumer build imports the generated client module. Affected component - Source (branch read): packages/@tinacms/cli/src/cmds/init/templates/config.ts lines 155–172 — reads VERCELGITCOMMITREF, GITHUBBRANCH, or HEAD into config.branch - Transform (URL build): packages/@tinacms/cli/src/next/codegen/index.ts lines 219–253 — createApiUrl() concatenates the raw branch into the API URL with no encodeURIComponent - Sink (template): packages/@tinacms/cli/src/next/codegen/index.ts lines 363–381 — genClient() interpolates the URL into url: '${apiURL}' - Sibling sink: packages/@tinacms/cli/src/next/codegen/codegen/plugin.ts line 55 — url: "${apiURL}" (same pattern, double quotes) Root cause The codegen template at index.ts:376 uses: where apiURL contains…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-pwhx-cvv3-qj5c
- Revision 2 · amended ·
Amended from osv record GHSA-pwhx-cvv3-qj5c
- Revision 1 · created ·
Published from ghsa record GHSA-pwhx-cvv3-qj5c
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-108259 Advisory: Tina: Code injection via unescaped Git branch name in generated client source IDs: CVE-2026-108259, GHSA-pwhx-cvv3-qj5c Record: https://patchnext.com/advisories/cve-2026-108259 (revision 3, source checked 26 Oct 2026, 13:07 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.2) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: @tinacms/cli 3.0.0. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @tinacms/cli: affected <= 2.7.0; fixed in 3.0.0 ## Suggested inspection (read-only) - `npm ls @tinacms/cli --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on @tinacms/cli. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-pwhx-cvv3-qj5c (GitHub-reviewed advisory GHSA-pwhx-cvv3-qj5c lists affected ranges: npm @tinacms/cli >=0 <=2.7.0) - Verified: https://osv.dev/vulnerability/GHSA-pwhx-cvv3-qj5c (OSV record GHSA-pwhx-cvv3-qj5c lists affected ranges: npm @tinacms/cli >=0 <3.0.0 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…