PyMdown Extensions is a set of extensions for the Python-Markdown markdown project. From 10.0.1 until 10.21.3, pymdownx.snippets uses a string-prefix containment check in SnippetPreprocessor.get_snippet_path() in pymdownx/snippets.py when restrict_base_path: True, allowing markdown snippet directives to read files from sibling paths that share the same base_path prefix, such as docs and docs_internal. This is a regression of CVE-2023-32309. This issue is fixed in version 10.21.3.
CVE-2026-46338
This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(medium)
- EG Risk
- 35(Track)EG Risk 35/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 17.8%
- KEV
- Not listed
Published
May 19, 2026
Last Modified
July 17, 2026
Advisory Details (3)
Auto-updated Jul 17, 2026Regression in pymdownx.snippets reintroduces sibling-prefix path traversal bypass despite restrict_base_path · Advisory · facelessuser/pymdown-extensions · GitHub
https://github.com/facelessuser/pymdown-extensions/security/advisories/GHSA-62q4-447f-wv8h10.21.3
Patch available: facelessuser/pymdown-extensions 10.21.3
https://github.com/facelessuser/pymdown-extensions/releases/tag/10.21.3commit 63b7835776d7 (facelessuser/pymdown-extensions)
Patch available: facelessuser/pymdown-extensions 10.21.3 (contains commit 63b7835776d7)
https://github.com/facelessuser/pymdown-extensions/commit/63b7835776d703d6c339cf2110d9888f676efc0cVendor Advisories for CVE-2026-46338(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| pymdown-extensions | 10.0.1 ... 10.9 (39 versions) | 10.21.3 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:17 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 23:29 UTCOSV refresh
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-05-24 06:13 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-46338?
When was CVE-2026-46338 disclosed?
Is CVE-2026-46338 actively exploited?
What is the CVSS score of CVE-2026-46338?
How do I remediate CVE-2026-46338?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46338
Is Your Infrastructure Affected by CVE-2026-46338?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.