CVE-2025-67843
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 · uneditedA Server-Side Template Injection (SSTI) vulnerability in the MDX Rendering Engine in Mintlify Platform before 2025-11-15 allows remote attackers to execute arbitrary code via inline JSX expressions in an MDX file.
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 confidenceA Server-Side Template Injection (SSTI) vulnerability in the MDX Rendering Engine of Mintlify Platform allows remote attackers to execute arbitrary code by injecting malicious inline JSX expressions within MDX files. This enables complete remote code execution without authentication, rated critical due to the CVSS score of 9.8.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2025-11-15CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 your Mintlify versionLocate the version information for your Mintlify deployment (typically found in package.json, package-lock.json, or the admin/settings panel of the Mintlify dashboard). Compare this version against the release date 2025-11-15.Affected if The installed version is dated before 2025-11-15 or the version number cannot be confirmed as the patched release.
-
Verify MDX rendering is enabledCheck your Mintlify configuration files (typically mint.json or similar configuration in your docs repository) for MDX-related settings. Look for whether MDX processing is explicitly enabled or allowed.Affected if MDX rendering is enabled and the Mintlify version is unpatched.
-
Identify accessible MDX endpointsReview your deployed documentation site to identify any routes that render MDX content. Check if MDX files (typically .mdx extensions) are served through publicly accessible URLs.Affected if MDX content is served over the network and the version is unpatched.
-
Audit custom MDX componentsExamine any custom MDX components or plugins configured in your Mintlify setup. Look for components that may accept user-supplied input and could be exploited through inline JSX expressions.Affected if Custom MDX components exist and the version is unpatched.
You are affected if your Mintlify deployment runs a version dated before 2025-11-15 and actively processes or serves 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 · scoped2025-11-15
Upgrade Mintlify Platform to version after 2025-11-15 to obtain the vendor patch. If immediate patching is not possible, restrict MDX file uploads or disable MDX rendering functionality until the patch can be applied.
Any Mintlify release dated 2025-11-15 or later
- Upgrade Mintlify to any version released on or after 2025-11-15, as this version includes the patch for the SSTI vulnerability in the MDX Rendering Engine.
- After upgrading, verify that MDX files with inline JSX expressions are rendered safely without arbitrary code execution.
- If self-hosted, ensure your deployment pulls the latest Mintlify version released after 2025-11-15.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67843 — 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-2025-67843 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