CVE-2026-74860

HIGHPre-NVD 8.58.5
EchelonGraph scoreHIGH confidence

Score 8.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-08. a secondary CVSS source baseline 8.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.5Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in libxml2 with Python bindings enabled. A remote attacker could exploit this vulnerability by providing a specially crafted XML document containing a Document Type Definition (DTD) with enumerated attribute values. This triggers a double-free error in the SAX attributeDecl callback handler, where a string is freed twice. This flaw can lead to a denial of service (DoS) due to a reproducible crash in Python applications using the libxml2 SAX bindings.

CVSS v3
8.5
EG Score
8.5(high)
EG Risk
38(Track)
EG Risk 38/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 computed
Severity85% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

September 8, 2026

Last Modified

September 10, 2026

Advisory Details (2)

Auto-updated Sep 8, 2026
Patch available. Sources: redhat.
redhat Patch Available

CVE-2026-74860 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-74860

Vendor Advisories for CVE-2026-74860(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatlibxml2-main-2.15.4-0.1.hum12026-09-06redhat

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 42× in last 7d / 78× 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-09-19 05:16 UTCEG score recompute
  2. 2026-09-19 05:16 UTCVendor advisory
  3. 2026-09-19 05:16 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 18:18 UTCVendor advisory
  6. 2026-09-18 18:18 UTCGHSA enrichment
  7. 2026-09-18 07:19 UTCVendor advisory
  8. 2026-09-18 07:19 UTCGHSA enrichment
  9. 2026-09-17 20:20 UTCEG score recompute
  10. 2026-09-17 20:20 UTCVendor advisory
  11. 2026-09-17 20:20 UTCGHSA enrichment
  12. 2026-09-17 06:58 UTCVendor advisory
  13. 2026-09-17 06:58 UTCGHSA enrichment
  14. 2026-09-16 19:59 UTCEG score recompute
  15. 2026-09-16 19:59 UTCVendor advisory
  16. 2026-09-16 19:59 UTCGHSA enrichment
  17. 2026-09-16 14:08 UTCEPSS rescore
  18. 2026-09-16 08:58 UTCEG score recompute
  19. 2026-09-16 08:58 UTCVendor advisory
  20. 2026-09-16 08:58 UTCGHSA enrichment
  21. 2026-09-16 05:15 UTCEPSS rescore
  22. 2026-09-15 21:30 UTCVendor advisory
  23. 2026-09-15 21:30 UTCGHSA enrichment
  24. 2026-09-15 10:31 UTCEG score recompute
  25. 2026-09-15 10:31 UTCVendor advisory
Show 53 more
  1. 2026-09-15 10:30 UTCGHSA enrichment
  2. 2026-09-15 03:12 UTCEPSS rescore
  3. 2026-09-14 23:30 UTCVendor advisory
  4. 2026-09-14 23:30 UTCGHSA enrichment
  5. 2026-09-14 12:11 UTCVendor advisory
  6. 2026-09-14 12:11 UTCGHSA enrichment
  7. 2026-09-14 01:12 UTCEG score recompute
  8. 2026-09-14 01:12 UTCVendor advisory
  9. 2026-09-14 01:12 UTCGHSA enrichment
  10. 2026-09-13 14:13 UTCVendor advisory
  11. 2026-09-13 14:13 UTCGHSA enrichment
  12. 2026-09-13 03:14 UTCVendor advisory
  13. 2026-09-13 03:14 UTCGHSA enrichment
  14. 2026-09-12 16:15 UTCEG score recompute
  15. 2026-09-12 16:15 UTCVendor advisory
  16. 2026-09-12 16:15 UTCGHSA enrichment
  17. 2026-09-12 15:02 UTCEPSS rescore
  18. 2026-09-12 05:15 UTCVendor advisory
  19. 2026-09-12 05:15 UTCGHSA enrichment
  20. 2026-09-11 18:16 UTCEG score recompute
  21. 2026-09-11 18:16 UTCVendor advisory
  22. 2026-09-11 18:16 UTCGHSA enrichment
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-11 07:17 UTCVendor advisory
  25. 2026-09-11 07:17 UTCGHSA enrichment
  26. 2026-09-10 20:18 UTCEG score recompute
  27. 2026-09-10 20:18 UTCVendor advisory
  28. 2026-09-10 20:18 UTCGHSA enrichment
  29. 2026-09-10 20:01 UTCEG score recompute
  30. 2026-09-10 20:01 UTCVendor advisory
  31. 2026-09-10 20:00 UTCGHSA enrichment
  32. 2026-09-10 12:29 UTCEG score recompute
  33. 2026-09-10 12:29 UTCVendor advisory
  34. 2026-09-10 12:29 UTCGHSA enrichment
  35. 2026-09-10 09:35 UTCEPSS rescore
  36. 2026-09-10 01:30 UTCVendor advisory
  37. 2026-09-10 01:30 UTCGHSA enrichment
  38. 2026-09-09 14:31 UTCEG score recompute
  39. 2026-09-09 14:30 UTCGHSA enrichment
  40. 2026-09-09 14:09 UTCGHSA enrichment
  41. 2026-09-09 13:39 UTCEG score recompute
  42. 2026-09-09 13:38 UTCGHSA enrichment
  43. 2026-09-09 12:26 UTCEG score recompute
  44. 2026-09-09 12:26 UTCGHSA enrichment
  45. 2026-09-09 11:20 UTCEG score recompute
  46. 2026-09-09 11:20 UTCGHSA enrichment
  47. 2026-09-09 06:49 UTCGHSA enrichment
  48. 2026-09-08 19:50 UTCGHSA enrichment
  49. 2026-09-08 13:37 UTCGHSA enrichment
  50. 2026-09-08 12:34 UTCEG score recompute
  51. 2026-09-08 12:34 UTCGHSA enrichment
  52. 2026-09-08 11:38 UTCEG score recompute
  53. 2026-09-08 11:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74860?
CVE-2026-74860 is a high vulnerability published on September 8, 2026. A flaw was found in libxml2 with Python bindings enabled. A remote attacker could exploit this vulnerability by providing a specially crafted XML document containing a Document Type Definition (DTD) with enumerated attribute values. This triggers a double-free error in the SAX attributeDecl…
When was CVE-2026-74860 disclosed?
CVE-2026-74860 was first published in the National Vulnerability Database on September 8, 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-74860 actively exploited?
CVE-2026-74860 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 70.8% of all scored CVEs.
What is the CVSS score of CVE-2026-74860?
CVE-2026-74860 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2026-74860?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74860, 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

Explore the affected products and dependency analysis for CVE-2026-74860

Explore →

Is Your Infrastructure Affected by CVE-2026-74860?

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