CVE-2025-67846 json
The Deployment Infrastructure in Mintlify Platform before 2025-11-15 allows remote attackers to bypass security patches and execute downgra…
published 2025-12-19 10 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-204424
- cvss
- 4.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 33%
- public exploits
- 0
- none known
Summary
The Deployment Infrastructure in Mintlify Platform before 2025-11-15 allows remote attackers to bypass security patches and execute downgrade attacks via predictable deployment identifiers on the Vercel preview domain. An attacker can identify the URL structure of a previous deployment that contains unpatched vulnerabilities. By browsing directly to the specific git-ref or deployment-id subdomain, the attacker can force the application to load the vulnerable version.
Patch / fix
- Mintlify Mintlify Platform 2025-11-15
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 10 mo ago
Exploit prediction
0.40% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- kibty.town https://kibty.town/blog/mintlify/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
Affected products
- Mintlify Mintlify Platform
Classification
- Weakness
-
- CWE-472 External Control of Assumed-Immutable Web Parameter
References
-
kibty.town
/blog/mintlify/
exploit, third-party-advisory
-
mintlify.com
/blog/working-with-security-researchers-november-2025
vendor-advisory
-
mintlify.com
/docs/changelog
release-notes
-
news.ycombinator.com
/item?id=46317098
issue-tracking
Sources
- CVE List CVE-2025-67846
- NVD CVE-2025-67846
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.