Skip to main content

Mistune EUVDEUVD-2026-108423

| CVE-2026-115354 HIGH
Path Traversal (CWE-22)
2026-10-22 disclosure@vulncheck.com GHSA-r6px-88r6-4rqg
7.1
CVSS 4.0 · Vendor: vulncheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Submit malicious Markdown file to app
  2. Delivery
    App renders file via Markdown.read()
  3. Exploit
    Include directive resolves traversal path
  4. Execution
    Mistune reads file outside document directory
  5. Impact
    Sensitive file contents disclosed in output

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK

2 techniques across 2 tactics: Discovery, Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires two specific, non-default conditions, both documented by the GHSA advisory: (1) the application must explicitly enable the opt-in Include directive via RSTDirective([Include()]); and (2) attacker-controlled Markdown must be rendered through Markdown.read(path), which seeds state.env['__file__'] from the caller-supplied file path - passing the Markdown as a plain string does NOT trigger the flaw. Under those conditions the include target is resolved with os.path.join(os.path.dirname(source_file), relpath) and os.path.normpath with no root restriction or allowlist, so relative (../secret.txt) or absolute (/etc/passwd) paths are read. Limiting factors: disclosure is bounded by files readable by the rendering process; the secondary HTML/script injection impact only applies when the included non-Markdown file contains markup (emitted unescaped inside <pre class="directive-include">). The only complete fix per the evidence is upgrading to Mistune 3.3.0.

Impact

The CVSS 4.0 base score is 7.1 (AV:N/AC:L/AT:N/PR:N/UI:P, impact VC:H only), indicating a network-reachable confidentiality issue requiring passive user/operator interaction and no attacker authentication. No EPSS probability and no KEV listing were supplied, and there is no CISA KEV entry, so there is no evidence of active exploitation; the exploitation status is that a complete, working public PoC exists (the GHSA advisory embeds a runnable exploit script plus example output disclosing /etc/passwd). The vuln.today Decision label is 'this_week', consistent with a serious but non-emergency item. The dominant risk-limiting factor is the integration precondition: the flaw only manifests when an application has explicitly opted into RSTDirective([Include()]) AND renders attacker-controlled Markdown via Markdown.read(path). This sharply narrows the real-world exposure relative to the 7.1 headline - most Mistune deployments do not enable the Include directive and do not feed attacker files through Markdown.read(). Where that pattern does exist, exploitation is trivial and reliable. Net: a genuine, well-documented local-file-disclosure (with secondary HTML/script injection) bug that is high priority for the specific integrations matching the precondition, but not a mass-exploitation threat for the general population. No signals conflict; the main caveat is that EPSS/KEV data were simply not provided and should not be read as 'low risk by omission'.

Exploit ScenarioDerived

An application enables Mistune's opt-in Include directive and lets untrusted users submit Markdown files that it renders via Markdown.read(path). An attacker uploads attacker.md containing .. include:: /etc/passwd (or a relative path like ../secret.txt); when the file is parsed, Mistune resolves the path, reads the target, and embeds its contents verbatim into the rendered output, disclosing the file and, if the included content contains markup, injecting unescaped HTML/script. A complete working PoC script demonstrating /etc/passwd disclosure is published in the GHSA advisory.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 22, 2026

Arbitrary local file read in Mistune's opt-in Include directive (all versions before 3.3.0, with 3.2.0 confirmed) lets an attacker who controls Markdown that an application renders through Markdown.read(path) disclose files readable by the rendering process - the advisory demonstrates reading /etc/passwd - and, when the included non-Markdown file contains markup, smuggle unescaped HTML or script into the rendered page. Exploitation requires two non-default conditions in the host application: the Include directive must be enabled via RSTDirective([Include()]), and the untrusted Markdown must be loaded from disk with Markdown.read(path); passing Markdown as a plain string does not trigger the flaw, and no public exploit is confirmed beyond the PoC reference published in the GHSA advisory. Confidentiality impact is the primary concern (assessed CVSS 3.1: AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N), and the vendor fix is Mistune 3.3.0.

RemediationAI

Upgrade to Mistune 3.3.0, the release identified as the only complete fix in the advisory (https://github.com/lepture/mistune/security/advisories/GHSA-jhcm-5rpf-j3wv); verify the installed version with pip show mistune or pip index versions and pin the minimum in your dependency constraints. If upgrading is temporarily blocked, the two exploit prerequisites can be removed: stop registering Include() through RSTDirective for any Markdown that untrusted users can influence, accepting that legitimate server-side include functionality is lost, and load untrusted documents as strings instead of via Markdown.read(path) so that state.env['__file__'] is never populated and the directive has no base path to traverse from - note that string-based rendering changes include resolution semantics for any remaining trusted use cases. Additionally, run the rendering process with a least-privilege account and restricted filesystem read access, since file disclosure is bounded by that process's permissions, and escape or sanitize rendered HTML output downstream if included files may contain markup, at the cost of additional processing and possible formatting changes for trusted content.

Affected VersionsENISA

mistune 0 <3.3.0

Affected Packages

euvd mistune fix: 3.3.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Mistune is a pure-Python Markdown parser; its reStructuredText-style directive extension ships an Include directive in src/mistune/directives/include.py that inlines the contents of another file at render time. The root cause is CWE-22 path traversal: when a document is loaded via Markdown.read(path), the library seeds state.env['__file__'] with the caller-supplied path, and Include.parse() resolves the directive target with os.path.join(os.path.dirname(source_file), relpath) followed by os.path.normpath, applying no root restriction, chroot-style confinement or allowlist before open(dest, 'rb'). Because normalization happens after joining, '.. include:: ../secret.txt' and absolute targets such as '/etc/passwd' both escape the document directory; disclosure is bounded only by the file permissions of the rendering process. A secondary issue is the rendering path: render_html_include() wraps the raw bytes in '<pre class="directive-include">' without escaping, so HTML or script content inside an included non-Markdown file survives literally into the output, giving limited content injection on top of the file read. The flaw is not a parser memory-safety bug and is not reachable through string-based rendering; it is entirely a consequence of path handling plus unescaped passthrough in that directive.

Know when Python gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (vulncheck) PRIMARY 7.1 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 7.1 HIGH

Remote attacker-supplied Markdown, no auth (PR:N), but rendering via opt-in Include needs operator action (UI:R); file disclosure gives C:H, unescaped script injection I:L.

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
Red Hat 6.5 MEDIUM

Primary rating from Vendor (vulncheck).

CVSS VectorVendor: vulncheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
Passive
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Oct 22, 2026 - 20:18 EUVD
CVE Published
Oct 22, 2026 - 19:17 cve.org
HIGH 7.1

DescriptionCVE.org

Mistune before 3.3.0 contains a path traversal vulnerability in the opt-in Include directive that allows attackers to read local files by supplying relative or absolute include paths. Attackers who submit Markdown rendered via Markdown.read() can disclose files such as /etc/passwd and inject unescaped HTML or script content into rendered output.

Technical POC Analysis

CWE-22 (Improper Limitation of a Pathname to a Restricted Directory / Path Traversal) in the opt-in reStructuredText Include directive of Mistune.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

A high-severity vulnerability in the Mistune Markdown rendering library, affecting all versions before 3.3.0, could allow attackers to read sensitive local files and inject malicious scripts into web pages when untrusted Markdown is processed through specific, non-default configurations. While exploitation requires two non-standard conditions and no active exploitation has been observed, the potential for data disclosure and cross-site scripting could impact customer trust and data confidentiality, warranting management attention.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 75% exploitable
Prevalence
Medium
popular Python Markdown library, but vulnerable Include feature is opt-in
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

More in Python

View all
CVE-2025-24016 CRITICAL POC
9.9 Feb 10

Wazuh SIEM platform versions 4.4.0 through 4.9.0 contain an unsafe deserialization vulnerability in the DistributedAPI t

CVE-2025-27520 CRITICAL POC
9.8 Apr 04

BentoML version 1.4.2 and earlier contains an unauthenticated remote code execution vulnerability through insecure deser

CVE-2025-2945 CRITICAL POC
9.9 Apr 03

pgAdmin 4 contains critical remote code execution vulnerabilities in the Query Tool download and Cloud Deployment endpoi

CVE-2013-5093 MEDIUM POC
6.8 Sep 27

The renderLocalView function in render/views.py in graphite-web in Graphite 0.9.5 through 0.9.10 uses the pickle Python

CVE-2025-32375 CRITICAL POC
9.8 Apr 09

BentoML is a Python library for building online serving systems optimized for AI apps and model inference. Rated critica

CVE-2014-0224 HIGH POC
7.4 Jun 05

OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph

CVE-2024-21644 HIGH POC
7.5 Jan 08

pyLoad download manager version prior to 0.5.0b3.dev77 exposes the Flask SECRET_KEY through an unauthenticated endpoint.

CVE-2026-33017 CRITICAL POC
9.3 Mar 17

Langflow (a visual LLM pipeline builder) contains a critical unauthenticated code execution vulnerability (CVE-2026-3301

CVE-2017-9462 HIGH POC
8.8 Jun 06

In Mercurial before 4.1.3, "hg serve --stdio" allows remote authenticated users to launch the Python debugger, and conse

CVE-2026-49869 CRITICAL POC
10.0 Jun 26

Unauthenticated remote code execution affects Kestra OSS (the open-source event-driven orchestration platform) prior to

CVE-2026-39987 CRITICAL POC
9.3 Apr 08

Unauthenticated remote code execution in Marimo ≤0.20.4 allows attackers to execute arbitrary system commands via the `/

CVE-2024-21645 MEDIUM POC
5.3 Jan 08

pyLoad is the free and open-source Download Manager written in pure Python. Rated medium severity (CVSS 5.3), this vulne

Vendor StatusVendor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy