LiveActive security incident?Get immediate response
CVE Record

CVE-2026-0969: Arbitrary code execution in React server-side rendering of untrusted MDX content

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.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-0969 affects server-side rendering of untrusted MDX content using next-mdx-remote. If an attacker can submit or influence MDX that is compiled by the vulnerable serialize function, the server may execute arbitrary code. The CVSS score is 8.8, reflecting high potential impact to confidentiality, integrity, and availability.

Executive priority

Treat as high priority where untrusted MDX is processed server-side. Affected systems could allow server code execution, creating material data and service risk. Prioritize internet-facing or multi-user content platforms first.

Technical view

The issue is CWE-94: improper control of code generation. next-mdx-remote’s serialize function insufficiently sanitizes MDX before compilation, enabling arbitrary code execution in React server-side rendering contexts. The record names HashiCorp Shared library version 4.3.0 and states the vulnerability is fixed in next-mdx-remote 6.0.0.

Likely exposure

Exposure is most likely in applications or shared libraries that compile untrusted MDX server-side using vulnerable next-mdx-remote serialize behavior. The source bundle specifically lists HashiCorp Shared library 4.3.0. Default status is otherwise listed as unaffected, so inventory confirmation is important.

Exploitation context

The CVSS vector indicates network reachability, low attack complexity, low privileges required, and no user interaction. The bundle does not state active exploitation, and KEV is false. Practical exploitability depends on whether attackers can supply or modify MDX that the server compiles.

Researcher notes

Evidence is limited to the CVE record and HashiCorp advisory reference. The bundle identifies the vulnerable function, impact, CVSS, one affected HashiCorp shared library version, and fixed next-mdx-remote version. No public exploit status is provided in the supplied sources.

Mitigation direction

  • Upgrade next-mdx-remote to 6.0.0 or a vendor-approved fixed version.
  • Review HashiCorp advisory HCSEC-2026-01 for product-specific guidance.
  • Do not server-render untrusted MDX until fixed or safely isolated.
  • Restrict who can submit or edit MDX content processed server-side.

Validation and detection

  • Inventory applications using next-mdx-remote serialize for server-side MDX compilation.
  • Check whether HashiCorp Shared library 4.3.0 is present.
  • Confirm next-mdx-remote is upgraded to 6.0.0 or later.
  • Identify MDX inputs that can be influenced by non-administrators.
  • Review logs for unexpected server-side MDX compilation activity.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-0969 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-0969Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HashiCorpShared library4.3.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.