CVE-2026-0969
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe serialize function in next-mdx-remote does not properly sanitize MDX content during compilation, allowing attackers to inject and execute arbitrary code through crafted MDX input.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if next-mdx-remote is installedCheck your project's package.json file under dependencies or devDependencies, or run 'npm list next-mdx-remote' or 'yarn list next-mdx-remote' to list the installed packageAffected if next-mdx-remote appears in your dependencies
-
Determine the installed version of next-mdx-remoteRun 'npm list next-mdx-remote' or 'yarn list next-mdx-remote' to see the exact version number installed, or inspect node_modules/next-mdx-remote/package.json for the version fieldAffected if The version is less than 6.0.0 (for example, 5.x.x, 4.x.x, etc.)
-
Check if your codebase imports or uses the serialize functionSearch your source code for imports from 'next-mdx-remote' such as 'import { serialize } from "next-mdx-remote/serialize"' or require statements like 'const { serialize } = require("next-mdx-remote/serialize")'Affected if The serialize function is imported and used in your code
-
Verify if user-controlled MDX content is passed to the serialize functionSearch your codebase for calls to the serialize function and trace whether the MDX input parameter comes from user input, external APIs, file uploads, or any untrusted sourceAffected if The serialize function is called with untrusted or user-supplied MDX content without additional sanitization
Your environment is affected if next-mdx-remote version is below 6.0.0 AND the serialize function processes untrusted or user-supplied MDX content
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade next-mdx-remote to version 6.0.0 or later to obtain the patched serialization logic.
- Upgrade the next-mdx-remote package to version 6.0.0 or later using your package manager (e.g., npm install next-mdx-remote@^6.0.0 or yarn add next-mdx-remote@^6.0.0)
- Test that MDX compilation and rendering still work correctly after the upgrade
- Verify that the serialize function behaves as expected with your existing MDX content
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0969 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0969 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data