CVE-2025-69534

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 40% 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).

Triggered by: NVD CVSS baseline
Sources: cna:github_m, epss
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

Python-Markdown version 3.8 contain a vulnerability where malformed HTML-like sequences can cause html.parser.HTMLParser to raise an unhandled AssertionError during Markdown parsing. Because Python-Markdown does not catch this exception, any application that processes attacker-controlled Markdown may crash. This enables remote, unauthenticated Denial of Service in web applications, documentation systems, CI/CD pipelines, and any service that renders untrusted Markdown. The issue was acknowledged by the vendor and fixed in version 3.8.1. This issue causes a remote Denial of Service in any application parsing untrusted Markdown, and can lead to Information Disclosure through uncaught exceptions.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
42.9%
KEV
Not listed

Published

March 5, 2026

Last Modified

June 30, 2026

Advisory Details (10)

Auto-updated Jul 2, 2026
Patch available. Sources: redhat.
generic

oss-security - CVE-2025-69534 in Python-Markdown

http://www.openwall.com/lists/oss-security/2026/03/06/4
generic

Security: CVE-2025-69534 – Remote DoS via malformed <![ sequence in Python-Markdown 3.8 · Issue #1534 · Python-Markdown/markdown · GitHub

https://github.com/Python-Markdown/markdown/issues/1534
generic

Bump version to 3.8.1 · Python-Markdown/markdown@3870f20 · GitHub

https://github.com/Python-Markdown/markdown/actions/runs/15736122892
generic

GitHub - Python-Markdown/markdown: A Python implementation of John Gruber’s Markdown with Extension support. · GitHub

https://github.com/Python-Markdown/markdown

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpython-markdown-0:3.5.1-6.el10_0.12026-05-26redhat
redhatpython-markdown-0:3.3.4-4.el9_6.22026-05-26redhat
redhatpython-markdown-0:3.3.4-4.el9_4.22026-05-26redhat
redhatpython-markdown-0:3.3.4-4.el9_8.22026-05-19redhat
redhatpython-markdown-0:3.5.1-6.el10_2.12026-05-19redhat
redhatpython-markdown-0:3.8.2-1.el9pc2026-05-07redhat
redhatpython3.12-markdown-0:3.8.2-1.el9pc2026-05-07redhat
redhatrhdh/rhdh-hub-rhel9:17779032622026-05-05redhat
redhatpython3.12-markdown-0:3.10.2-1.el9ap2026-05-04redhat
redhatrhoai/odh-training-rocm62-torch25-py311-rhel9:17762722532026-04-23redhat
redhatrhdh/rhdh-hub-rhel9:17767842862026-04-22redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
markdown1.7 ... 3.8 (54 versions)

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 60× 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-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-05 02:30 UTCEPSS rescore
  4. 2026-07-05 02:30 UTCEPSS rescore
  5. 2026-07-04 06:31 UTCEPSS rescore
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-01 15:06 UTCEPSS rescore
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-30 23:22 UTCEPSS rescore
  10. 2026-06-30 04:31 UTCNVD updateseverity → HIGH
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-29 08:02 UTCOSV refresh
  14. 2026-06-28 14:07 UTCEPSS rescore
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-27 03:08 UTCEPSS rescore
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-24 14:05 UTCEPSS rescore
  22. 2026-06-24 14:04 UTCEPSS rescore
  23. 2026-06-23 21:32 UTCEPSS rescore
  24. 2026-06-22 14:25 UTCEPSS rescore
  25. 2026-06-22 14:25 UTCEPSS rescore
Show 40 more
  1. 2026-06-21 14:56 UTCEPSS rescore
  2. 2026-06-21 14:56 UTCEPSS rescore
  3. 2026-06-21 01:59 UTCEPSS rescore
  4. 2026-06-21 01:59 UTCEPSS rescore
  5. 2026-06-19 19:25 UTCEPSS rescore
  6. 2026-06-19 19:25 UTCEPSS rescore
  7. 2026-06-18 17:52 UTCEPSS rescore
  8. 2026-06-18 17:52 UTCEPSS rescore
  9. 2026-06-17 17:53 UTCEPSS rescore
  10. 2026-06-16 17:52 UTCEPSS rescore
  11. 2026-06-15 17:48 UTCEPSS rescore
  12. 2026-06-14 23:18 UTCEPSS rescore
  13. 2026-06-13 23:00 UTCEPSS rescore
  14. 2026-06-13 23:00 UTCEPSS rescore
  15. 2026-06-12 23:12 UTCEPSS rescore
  16. 2026-06-12 23:12 UTCEPSS rescore
  17. 2026-06-12 00:40 UTCEG score recompute
  18. 2026-06-12 00:40 UTCVendor advisory
  19. 2026-06-11 14:00 UTCEPSS rescore
  20. 2026-06-10 22:18 UTCEPSS rescore
  21. 2026-06-10 18:51 UTCEG score recompute
  22. 2026-06-10 18:51 UTCVendor advisory
  23. 2026-06-10 13:22 UTCEPSS rescore
  24. 2026-06-10 06:26 UTCEG score recompute
  25. 2026-06-10 06:26 UTCVendor advisory
  26. 2026-06-09 17:43 UTCEG score recompute
  27. 2026-06-09 17:43 UTCVendor advisory
  28. 2026-06-08 14:17 UTCEPSS rescore
  29. 2026-06-08 14:17 UTCEPSS rescore
  30. 2026-06-08 03:15 UTCEG score recompute
  31. 2026-06-08 03:15 UTCVendor advisory
  32. 2026-06-07 15:31 UTCEG score recompute
  33. 2026-06-07 15:31 UTCVendor advisory
  34. 2026-06-07 15:24 UTCEPSS rescore
  35. 2026-06-07 15:24 UTCEPSS rescore
  36. 2026-06-06 13:47 UTCEPSS rescore
  37. 2026-06-06 13:47 UTCEPSS rescore
  38. 2026-06-06 00:53 UTCEG score recompute
  39. 2026-06-06 00:53 UTCVendor advisory
  40. 2026-06-06 00:53 UTCOSV refresh

Frequently asked(5)

What is CVE-2025-69534?
CVE-2025-69534 is a high vulnerability published on March 5, 2026. Python-Markdown version 3.8 contain a vulnerability where malformed HTML-like sequences can cause html.parser.HTMLParser to raise an unhandled AssertionError during Markdown parsing. Because Python-Markdown does not catch this exception, any application that processes attacker-controlled Markdown…
When was CVE-2025-69534 disclosed?
CVE-2025-69534 was first published in the National Vulnerability Database on March 5, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-69534 actively exploited?
CVE-2025-69534 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 42.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-69534?
CVE-2025-69534 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2025-69534?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-69534, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-69534

Explore →

Is Your Infrastructure Affected by CVE-2025-69534?

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