Cyber Resilience

CVE-2025-67843

Mintlify ≤ 2025-11-15

Public PoC
Published
19 December 2025
Modified
02 January 2026
Patch / advisory
View advisory
CVSS Score v3.1 8.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
EPSS Score 0.011 63th percentile
Risk Priority 63 floored blend · peak EPSS

Summary

CVE-2025-67843 is a high-severity Improper Neutralization of Special Elements Used in a Template Engine (CWE-1336) vulnerability in Mintlify Mintlify. Its CVSS base score is 8.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Template Injection (T1221); ranked in the top 37% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-67843 is a Server-Side Template Injection (SSTI) vulnerability, classified under CWE-1336, affecting the MDX Rendering Engine in the Mintlify Platform prior to version 2025-11-15. It enables remote attackers to execute arbitrary code by injecting inline JSX expressions into an MDX file. The vulnerability carries a CVSS v3.1 base score of 8.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L), indicating high severity due to its network accessibility, low attack complexity, and potential for high confidentiality and integrity impacts with low availability disruption.

Attackers with low privileges, such as authenticated users on the Mintlify Platform, can exploit this vulnerability remotely without user interaction. By crafting malicious inline JSX expressions within an MDX file, they achieve arbitrary code execution on the server, potentially leading to data breaches, modification of platform content, or limited denial-of-service effects.

Mitigation details are available in vendor advisories, including Mintlify's changelog at https://www.mintlify.com/docs/changelog and their blog post on working with security researchers at https://www.mintlify.com/blog/working-with-security-researchers-november-2025. Security practitioners should ensure deployment of Mintlify Platform version 2025-11-15 or later to address the issue, as earlier versions remain vulnerable. Additional analysis appears in references such as https://kibty.town/blog/mintlify/ and Hacker News discussion at https://news.ycombinator.com/item?id=46317098.

EU & UK References

Vulnerability Data

A 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.

CWE(s)
CWE-1336

Related Threats

MITRE ATT&CK Enterprise Techniques

T1221 Template Injection Stealth
Adversaries may create or modify references in user document templates to conceal malicious code or force authentication attempts.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-67842Same product: Mintlify Mintlify
CVE-2025-67844Same product: Mintlify Mintlify
CVE-2025-67846Same product: Mintlify Mintlify
CVE-2025-67845Same product: Mintlify Mintlify
CVE-2025-64087Shared CWE-1336
CVE-2026-44916Shared CWE-1336
CVE-2025-49136Shared CWE-1336
CVE-2025-32461Shared CWE-1336
CVE-2024-8238Shared CWE-1336
CVE-2025-57811Shared CWE-1336

Affected Assets

mintlify
mintlify
≤ 2025-11-15

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.2
  • V1.3.7
  • V1.3.10

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and static analysis can discover missing neutralization of template directives.

SI-10 Information Input Validation good match

Input validation rejects or sanitizes untrusted data before it reaches the template engine, stopping injection of special syntax.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles require use of safe templating APIs and proper escaping of external input.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper input neutralization in template engines to prevent injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect template-injection flaws but does not itself implement neutralization controls.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and sanitization that directly prevents template-injection weaknesses.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for neutralizing special elements in template engines.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the likelihood of unsafe template processing but do not prescribe specific neutralization techniques.

A.8.28 Secure coding partial match
prevents

Secure coding standards require proper escaping or sandboxing of template directives, directly mitigating CWE-1336.

References