VulnerabilityPublished 19 Dec 2025

CVE-2025-67845: Mintlify Platform · Path Traversal: '../filedir

Affects Mintlify PlatformSource CVE Database V5

Not known to be exploited · CVSS 6.4 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

6.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 43% 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:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

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

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Mintlify Mintlify Platform	Affected =0	Fixed in–

AI-suggested

Organizations should immediately update the Mintlify Platform to the patched version released after 2025-11-15. In the absence of a patch, implement strict input validation and sanitization on all URL parameters to prevent path traversal sequences. Employ allowlisting of acceptable file paths and reject any input containing '../' or similar traversal patterns. Restrict access to the Static Asset Proxy Endpoint to trusted users and networks where possible, and enforce the principle of least privilege to limit the impact of compromised accounts. Conduct thorough code reviews and penetration testing focused on directory traversal and injection vulnerabilities. Monitor logs for suspicious access patterns or attempts to exploit path traversal. Additionally, implement Content Security Policy (CSP) headers to mitigate the impact of any injected scripts. Educate developers and administrators about secure coding practices related to file path handling. Finally, maintain an incident response plan to quickly address any exploitation attempts.

Description

A Directory Traversal vulnerability in the Static Asset Proxy Endpoint in Mintlify Platform before 2025-11-15 allows remote attackers to inject arbitrary web script or HTML via a crafted URL containing path traversal sequences.

Impact

For European organizations, especially those relying on the Mintlify Platform for documentation or developer tools, this vulnerability could lead to unauthorized access to sensitive files or injection of malicious content into web assets. This may result in partial data leakage, defacement, or the facilitation of further attacks such as XSS, which can compromise user sessions or credentials. The impact is particularly relevant for organizations handling sensitive intellectual property or customer data within their documentation or static assets. Since the vulnerability requires limited privileges but no user interaction, insider threats or compromised accounts could exploit this flaw to escalate attacks. The medium severity indicates a moderate risk, but the scope change means that the vulnerability could affect multiple components or users once exploited. Disruption of service is unlikely, but reputational damage and compliance risks (e.g., GDPR) due to data exposure are concerns. Organizations in sectors such as finance, technology, and government in Europe should be vigilant, as attackers may target these high-value entities.

CWE-24Path Traversal: '../filedir' (opens in a new tab)
Variant weakness
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "../" sequences that can resolve to a location that is outside of that directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Dec 2025, 04:29 UTC

WeaknessesCWE-24

Technical details

References

Community reviews

Related threats