Arbitrary code execution in React server-side rendering of untrusted MDX content

published 2026-02-12 8 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-7026 , GHSA-g4xw-jxrg-5f6m

cvss: 8.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits: 0; none known

The serialize function used to compile MDX in next-mdx-remote is vulnerable to arbitrary code execution due to insufficient sanitization of MDX content. This vulnerability, CVE-2026-0969, is fixed in next-mdx-remote 6.0.0.

Patch / fix

fixed in 2 links 2

npm next-mdx-remote 6.0.0
HashiCorp Shared library 6.0.0

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 8 mo ago (2026-02-12)

Exploit prediction

0.64% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.8	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
GitHub	3.1	8.8	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
npm	next-mdx-remote	>=4.3.0, <6.0.0	6.0.0

Affected products

HashiCorp Shared library

Classification

Weakness

CWE-94 Improper Control of Generation of Code

References

Sources

CVE List CVE-2026-0969
GitHub Advisory GHSA-g4xw-jxrg-5f6m
NVD CVE-2026-0969

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary