Tina is a headless content management system. @tinacms/cli versions prior to 2.4.3 contain a Remote Code Execution vulnerability in the Forestry-to-Tina migration command. The internal helper addVariablesToCode unquotes any value matching the marker "__TINA_INTERNAL__:::(.*?):::" inside the stringified collection JSON. User-supplied label and name fields from .forestry/**/*.yml are placed into that JSON without any sanitisation. An attacker who controls a Forestry-style project can therefore inject arbitrary JavaScript into the generated tina/templates.{ts,js} file. The injected code is written at module top level, so it executes the moment the developer runs tinacms dev or tinacms build, with the developer's privileges. This issue has been fixed in version 2.4.3.
CVE-2026-54074
This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(medium)
- EPSS
- 6.7%
- KEV
- Not listed
Published
June 19, 2026
Last Modified
July 2, 2026
Advisory Details (1)
Auto-updated Jul 1, 2026Remote Code Execution in @tinacms/cli via Forestry migration — unsanitised __TINA_INTERNAL__ marker in user-controlled YAML labels · Advisory · tinacms/tinacms · GitHub
https://github.com/tinacms/tinacms/security/advisories/GHSA-4936-9hrh-qqpwVendor Advisories for CVE-2026-54074(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @tinacms/cli | — | 2.4.3 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 23× in last 7d / 45× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-07 01:15 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 13:51 UTCEG score recompute
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:18 UTCEG score recompute
- 2026-07-05 14:54 UTCEG score recompute
- 2026-07-05 03:15 UTCEG score recompute
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 15:50 UTCEG score recompute
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 04:20 UTCEG score recompute
- 2026-07-03 16:38 UTCEG score recompute
- 2026-07-03 05:13 UTCEG score recompute
- 2026-07-02 17:44 UTCEG score recompute
- 2026-07-02 06:19 UTCEG score recompute
- 2026-07-01 18:53 UTCEG score recompute
- 2026-07-01 07:29 UTCEG score recompute
- 2026-06-30 20:05 UTCEG score recompute
- 2026-06-30 08:41 UTCEG score recompute
- 2026-06-29 21:17 UTCEG score recompute
- 2026-06-29 09:53 UTCEG score recompute
Show 20 moreShow fewer
- 2026-06-28 22:29 UTCEG score recompute
- 2026-06-28 11:05 UTCEG score recompute
- 2026-06-27 23:40 UTCEG score recompute
- 2026-06-27 12:15 UTCEG score recompute
- 2026-06-27 00:50 UTCEG score recompute
- 2026-06-26 13:26 UTCEG score recompute
- 2026-06-26 02:02 UTCEG score recompute
- 2026-06-25 14:38 UTCEG score recompute
- 2026-06-25 03:14 UTCEG score recompute
- 2026-06-24 15:49 UTCEG score recompute
- 2026-06-24 04:24 UTCEG score recompute
- 2026-06-23 16:59 UTCEG score recompute
- 2026-06-23 05:29 UTCEG score recompute
- 2026-06-22 18:02 UTCEG score recompute
- 2026-06-22 06:29 UTCEG score recompute
- 2026-06-21 19:01 UTCEG score recompute
- 2026-06-21 07:37 UTCEG score recompute
- 2026-06-20 20:13 UTCEG score recompute
- 2026-06-20 08:48 UTCEG score recompute
- 2026-06-19 21:23 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-94
- CVE-2006-1359NVD 0.0EG 9.0EPSS 99%NONE
- CVE-2005-1921NVD 0.0EG 9.0EPSS 100%NONE
- CVE-2005-3302EG 7.3HIGH
- CVE-2005-1876EG 4.5MEDIUM
- CVE-2003-1599EG 0.0NONE
- CVE-2006-1318EG 0.0EPSS 96%NONE
- CVE-2006-1301EG 0.0EPSS 95%NONE
- CVE-2006-1308EG 0.0EPSS 95%NONE
- CVE-2006-1309EG 0.0EPSS 95%NONE
- CVE-2006-1304EG 0.0EPSS 95%NONE
Frequently asked(5)
What is CVE-2026-54074?
When was CVE-2026-54074 disclosed?
Is CVE-2026-54074 actively exploited?
What is the CVSS score of CVE-2026-54074?
How do I remediate CVE-2026-54074?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54074
Is Your Infrastructure Affected by CVE-2026-54074?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.