CVE-2025-67843: Mintlify Platform · Template Injection
Affects Mintlify PlatformSource CVE Database V5
Not known to be exploited · CVSS 8.3 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 65% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 19 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Mintlify Mintlify Platform | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-67843, organizations should: 1) Monitor Mintlify’s official channels closely for patches and apply updates immediately once released. 2) Implement strict input validation and sanitization on all MDX files uploaded or processed, specifically filtering or disallowing inline JSX expressions. 3) Restrict access to the MDX rendering functionality to trusted users and environments, employing role-based access controls to limit privileges. 4) Employ runtime application self-protection (RASP) or web application firewalls (WAFs) configured to detect and block suspicious template injection patterns. 5) Conduct regular security audits and code reviews focusing on template rendering components. 6) Isolate the rendering environment using containerization or sandboxing to limit the impact of potential exploitation. 7) Educate developers and content contributors about the risks of injecting untrusted code into MDX files. 8) Monitor logs and network traffic for unusual activity related to MDX processing to detect early signs of exploitation attempts.
Description
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.