CVE-2026-61632

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.3Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

PyMdown Extensions is a set of extensions for the Python-Markdown markdown project. In versions up to and including 10.21.3, the b64 extension is vulnerable to a path traversal that discloses arbitrary files: it inlines images referenced by by joining the src onto the configured base_path with os.path.normpath and opening the result directly, without verifying that the resolved path stays inside base_path. As a result, an src containing ../ sequences or an absolute path reads a file outside base_path as long as it has an allowed image extension (.png, .jpg, .jpeg, .gif, .svg), and the file's contents are then base64-encoded into the rendered output, disclosing them. An application that renders untrusted Markdown with pymdownx.b64 enabled can therefore leak the contents of image-extension files readable by the process to whoever controls the Markdown or views the output, a targeted file-read bounded by the extension check. This issue has been fixed in version 11.0.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
55
EG Risk 55/100CISA SSVC

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 computed
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 24, 2026

Last Modified

September 10, 2026

Advisory Details (2)

Auto-updated Aug 6, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
githubMentions a patch (unverified)🟡 PoC Available

Path traversal in the b64 extension lets <img src> read files outside base_path · Advisory · facelessuser/pymdown-extensions · GitHub

https://github.com/facelessuser/pymdown-extensions/security/advisories/GHSA-9xwg-3r6f-jcx2
github_release Patch Available

11.0

Patch available: facelessuser/pymdown-extensions 11.0

https://github.com/facelessuser/pymdown-extensions/releases/tag/11.0

Vendor Advisories for CVE-2026-61632(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
pymdown-extensions10.11.2-1 ... 9.5-5 (14 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pymdown-extensions10.13-1 ... 11.0.1-1 (8 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pymdown-extensions10.13-1 ... 10.19.1-3 (6 versions)
  • every version up to 11.0.1-1: fixed in 11.0.1-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pymdown-extensions1.0.0 ... 9.9.2 (118 versions)
  • every version up to 11.0.0: fixed in 11.0.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 34× 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.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:13 UTCEPSS rescore
  4. 2026-10-07 23:48 UTCEPSS rescore
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-05 17:43 UTCEPSS rescore
  7. 2026-10-04 23:22 UTCEPSS rescore
  8. 2026-10-04 07:42 UTCEG score recompute
  9. 2026-10-03 14:26 UTCEPSS rescore
  10. 2026-10-03 03:18 UTCEG score recompute
  11. 2026-10-02 17:56 UTCEPSS rescore
  12. 2026-10-01 19:50 UTCEPSS rescore
  13. 2026-10-01 05:59 UTCEG score recompute
  14. 2026-09-30 15:03 UTCEPSS rescore
  15. 2026-09-28 13:51 UTCEPSS rescore
  16. 2026-09-28 04:27 UTCEG score recompute
  17. 2026-09-26 15:59 UTCEPSS rescore
  18. 2026-09-25 10:07 UTCEG score recompute
  19. 2026-09-24 00:55 UTCEG score recompute
  20. 2026-09-23 17:54 UTCEPSS rescore
  21. 2026-09-22 22:13 UTCEG score recompute
  22. 2026-09-20 20:16 UTCEPSS rescore
  23. 2026-09-20 01:39 UTCEG score recompute
  24. 2026-09-18 19:28 UTCEPSS rescore
  25. 2026-09-18 02:59 UTCEG score recompute
Show 66 more
  1. 2026-09-16 14:08 UTCEPSS rescore
  2. 2026-09-16 11:58 UTCEG score recompute
  3. 2026-09-16 05:15 UTCEPSS rescore
  4. 2026-09-15 09:36 UTCEG score recompute
  5. 2026-09-14 05:06 UTCEG score recompute
  6. 2026-09-13 02:58 UTCEG score recompute
  7. 2026-09-12 00:49 UTCEG score recompute
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 09:37 UTCEPSS rescore
  10. 2026-09-10 13:36 UTCEG score recompute
  11. 2026-09-09 08:45 UTCEG score recompute
  12. 2026-09-08 22:01 UTCEPSS rescore
  13. 2026-09-07 21:24 UTCEG score recompute
  14. 2026-09-07 16:01 UTCEPSS rescore
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-05 19:23 UTCEG score recompute
  17. 2026-09-04 12:51 UTCEG score recompute
  18. 2026-09-04 05:07 UTCEPSS rescore
  19. 2026-09-02 14:12 UTCEPSS rescore
  20. 2026-09-01 23:16 UTCEG score recompute
  21. 2026-09-01 13:54 UTCEPSS rescore
  22. 2026-09-01 04:40 UTCEPSS rescore
  23. 2026-08-31 02:26 UTCEG score recompute
  24. 2026-08-30 19:17 UTCEPSS rescore
  25. 2026-08-30 01:22 UTCEPSS rescore
  26. 2026-08-30 00:17 UTCEG score recompute
  27. 2026-08-28 21:42 UTCEPSS rescore
  28. 2026-08-27 14:25 UTCEPSS rescore
  29. 2026-08-27 12:48 UTCEG score recompute
  30. 2026-08-26 14:46 UTCEPSS rescore
  31. 2026-08-26 10:39 UTCEG score recompute
  32. 2026-08-25 13:49 UTCEPSS rescore
  33. 2026-08-25 07:44 UTCEG score recompute
  34. 2026-08-23 03:27 UTCEG score recompute
  35. 2026-08-23 00:19 UTCEPSS rescore
  36. 2026-08-22 01:19 UTCEG score recompute
  37. 2026-08-21 23:49 UTCEPSS rescore
  38. 2026-08-20 23:10 UTCEG score recompute
  39. 2026-08-20 22:55 UTCEPSS rescore
  40. 2026-08-19 21:02 UTCEG score recompute
  41. 2026-08-19 17:04 UTCEPSS rescore
  42. 2026-08-18 18:52 UTCEG score recompute
  43. 2026-08-18 13:48 UTCEPSS rescore
  44. 2026-08-17 13:47 UTCEPSS rescore
  45. 2026-08-17 13:41 UTCEG score recompute
  46. 2026-08-16 14:56 UTCEPSS rescore
  47. 2026-08-16 11:33 UTCEG score recompute
  48. 2026-08-15 09:25 UTCEG score recompute
  49. 2026-08-15 01:30 UTCEPSS rescore
  50. 2026-08-14 07:17 UTCEG score recompute
  51. 2026-08-13 22:00 UTCEPSS rescore
  52. 2026-08-13 05:08 UTCEG score recompute
  53. 2026-08-12 13:51 UTCEPSS rescore
  54. 2026-08-12 03:00 UTCEG score recompute
  55. 2026-08-11 00:52 UTCEG score recompute
  56. 2026-08-11 00:00 UTCEPSS rescore
  57. 2026-08-09 22:44 UTCEG score recompute
  58. 2026-08-09 13:47 UTCEPSS rescore
  59. 2026-08-08 20:36 UTCEG score recompute
  60. 2026-08-08 16:37 UTCEPSS rescore
  61. 2026-08-07 18:28 UTCEG score recompute
  62. 2026-08-07 17:28 UTCEG score recompute
  63. 2026-08-06 22:25 UTCEG score recompute
  64. 2026-07-30 18:48 UTCEG score recompute
  65. 2026-07-27 11:52 UTCEG score recompute
  66. 2026-07-24 17:13 UTCEG score recompute

Related CVEs(same product + same CWE)

Same product

4 shown

Debian:12:pymdown-extensions · Debian:13:pymdown-extensions

Frequently asked(5)

What is CVE-2026-61632?
CVE-2026-61632 is a medium vulnerability published on July 24, 2026. PyMdown Extensions is a set of extensions for the Python-Markdown markdown project. In versions up to and including 10.21.3, the b64 extension is vulnerable to a path traversal that discloses arbitrary files: it inlines images referenced by <img src="..."> by joining the src onto the configured…
When was CVE-2026-61632 disclosed?
CVE-2026-61632 was first published on July 24, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61632 actively exploited?
CVE-2026-61632 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61632?
CVE-2026-61632 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61632?
A fix for CVE-2026-61632 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-61632 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61632

Explore →

Is Your Infrastructure Affected by CVE-2026-61632?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs