CVE
@tinacms/mdx before 2.4.2 Code Injection via MDX Serializer Rich-Text Values
- Exploited
- No known exploitation
- Fix
- Fixed in 2.4.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Uses @tinacms/mdx before 2.4.2 Rich-text components with list fields or a highlight colour are serialized through the affected code paths The stored MDX is evaluated (client side, at build, or on SSR); sites that only render through TinaMarkdown are not affected
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Authenticated content editors of @tinacms/mdx can save crafted rich-text values over the network that break out of MDX expressions in stored .mdx files, letting an attacker run JavaScript in visitors' browsers or on build and server-side rendering hosts. The attacker needs only low-privilege editor access and no user interaction.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
@tinacms/mdx before 2.4.2 contains a code injection vulnerability in its MDX serializer, which writes rich-text values into MDX expressions without escaping them. Authenticated content editors can save crafted values that break out of list field or highlightColor expressions in the stored .mdx file, executing JavaScript in visitors' browsers or on build and server-side rendering hosts.
Who should check
Teams shipping @tinacms/mdx before 2.4.2 whose sites evaluate MDX in the browser or compile it on build or SSR hosts.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 8.8
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Uses @tinacms/mdx before 2.4.2 Rich-text components with list fields or a highlight colour are serialized through the affected code paths The stored MDX is evaluated (client side, at build, or on SSR); sites that only render through TinaMarkdown are not affectedUpgrade to a fixed version: 2.4.2.
Workaround: Render rich text with TinaMarkdown instead of evaluating the MDX, and give editor access only to trusted users.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126774 (@tinacms/mdx before 2.4.2 Code Injection via MDX Serializer Rich-Text Values), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126774 (entry last updated 2026-11-11):
Affected:
- tinacms @tinacms/mdx: fixed in 2.4.2
Fixed versions: 2.4.2.
Conditions (all must be true for the bug to be hit):
- Uses @tinacms/mdx before 2.4.2 (source: https://www.vulncheck.com/advisories/tinacms-mdx-before-2.4.2-code-injection-via-mdx-serializer-rich-text-values)
- Rich-text components with list fields or a highlight colour are serialized through the affected code paths (source: https://github.com/tinacms/tinacms/security/advisories/GHSA-6vw5-w22x-ghxv)
- The stored MDX is evaluated (client side, at build, or on SSR); sites that only render through TinaMarkdown are not affected (source: https://github.com/tinacms/tinacms/security/advisories/GHSA-6vw5-w22x-ghxv)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
Workaround: Render rich text with TinaMarkdown instead of evaluating the MDX, and give editor access only to trusted users. (source: https://github.com/tinacms/tinacms/security/advisories/GHSA-6vw5-w22x-ghxv)
CISA KEV: CVE-2026-126774 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126774 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/tinacms/tinacms/security/advisories/GHSA-6vw5-w22x-ghxv
- https://github.com/tinacms/tinacms/pull/7958
- https://github.com/tinacms/tinacms/commit/19285c6deeee52c380e8b2fdeafedc9530dc0618
- https://github.com/tinacms/tinacms/releases/tag/%40tinacms/mdx%402.4.2
- https://github.com/tinacms/tinacms/blob/%40tinacms/mdx%400.60.3/packages/%40tinacms/mdx/src/stringify/acorn.ts#L81
- https://www.vulncheck.com/advisories/tinacms-mdx-before-2.4.2-code-injection-via-mdx-serializer-rich-text-values
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126774
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126774"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- tinacms @tinacms/mdx
fixed in 2.4.2
Evidence 8
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Patch
- Patch
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126774
Is CVE-2026-126774 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Rich-text components with list fields or a highlight colour are serialized into MDX without proper escaping, so content typed by an editor can carry JavaScript that runs outside the editor's trust boundary. The stored MDX can then execute in visitors' browsers or on build and SSR servers.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-126774?
@tinacms/mdx: before 2.4.2.Source: cve.now feed data
Am I affected, and how do I check?
Versions of @tinacms/mdx before 2.4.2 are affected, but only where the stored MDX is evaluated (client side, at build, or on SSR). Sites that render rich text only through Tina's TinaMarkdown component, with no MDX evaluation, are not affected. To check, look at the installed @tinacms/mdx version in your lockfile or package.json and at whether your site evaluates MDX.Source: vulncheck.com, github.com
How do I fix CVE-2026-126774?
Upgrade @tinacms/mdx to 2.4.2 or later, which contains the fix. Until then, limit editor access to trusted users.Source: vulncheck.com, github.com