CVE-2024-56171

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-02-19. NVD baseline CVSS 7.8; sources differ by 0.0.

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

A fix is available — apply it.

libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a use-after-free in xmlSchemaIDCFillNodeTables and xmlSchemaBubbleIDCNodeTables in xmlschemas.c. To exploit this, a crafted XML document must be validated against an XML schema with certain identity constraints, or a crafted XML schema must be used.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
36(Track)
EG Risk 36/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
Severity78% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
63%
KEV
Not listed

Published

February 18, 2025

Last Modified

November 3, 2025

References (11)

Vendor Advisories for CVE-2024-56171(20)

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

Patch Availability(25)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython-libxml2 (2.9.1+dfsg1-3ubuntu4.13+esm7) @ trusty2026-05-30ubuntu
redhatservice-interconnect/skupper-site-controller-rhel9:1.4.8-12025-06-30redhat
redhatlibxml2-0:2.12.5-5.el10_02025-05-13redhat
redhatservice-interconnect/skupper-site-controller-rhel9:1.8.5-12025-04-17redhat
redhatnetwork-observability/network-observability-rhel9-operator:1.8-17441125012025-04-14redhat
redhatrhcos-412.86.202503310142-02025-04-10redhat
redhatrhcos-414.92.202504010153-02025-04-09redhat
redhatrhcos-416.94.202503252048-02025-04-03redhat
redhatlibxml22025-04-02redhat
redhatrhoai/odh-notebook-controller-rhel8:v2.16.2-17424872252025-03-31redhat
redhatrhcos-415.92.202503190057-02025-03-26redhat
redhatrhcos-417.94.202503172033-02025-03-26redhat
redhatrhcos-418.94.202503181639-02025-03-25redhat
redhatrhcos-413.92.202503112237-02025-03-20redhat
redhatrhosdt/opentelemetry-target-allocator-rhel8:rhosdt-3.52025-03-13redhat
redhatlibxml2-0:2.9.1-6.el7_9.92025-03-12redhat
redhatlibxml2-0:2.9.7-19.el8_102025-03-12redhat
redhatlibxml2-0:2.9.13-6.el9_5.22025-03-12redhat
redhatlibxml2-0:2.9.13-9.el9_42025-03-12redhat
redhatlibxml2-0:2.9.7-9.el8_4.52025-03-11redhat
redhatlibxml2-0:2.9.7-9.el8_2.12025-03-11redhat
redhatlibxml2-0:2.9.13-1.el9_0.42025-03-10redhat
redhatlibxml2-0:2.9.7-16.el8_8.72025-03-10redhat
redhatlibxml2-0:2.9.7-13.el8_6.82025-03-10redhat
redhatlibxml2-0:2.9.13-3.el9_2.62025-03-10redhat

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.

Additional Vendor Advisories

(6)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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-25 14:17 UTCEPSS rescore
  2. 2026-07-25 14:17 UTCEPSS rescore
  3. 2026-07-24 15:11 UTCOSV refresh
  4. 2026-07-24 14:16 UTCEPSS rescore
  5. 2026-07-23 14:17 UTCEPSS rescore
  6. 2026-07-23 14:17 UTCEPSS rescore
  7. 2026-07-23 02:44 UTCEG score recompute
  8. 2026-07-22 14:07 UTCEPSS rescore
  9. 2026-07-21 15:23 UTCEPSS rescore
  10. 2026-07-20 17:07 UTCEPSS rescore
  11. 2026-07-19 14:30 UTCEPSS rescore
  12. 2026-07-19 14:30 UTCEPSS rescore
  13. 2026-07-19 02:28 UTCEPSS rescore
  14. 2026-07-19 02:28 UTCEPSS rescore
  15. 2026-07-18 10:03 UTCEPSS rescore
  16. 2026-07-16 17:02 UTCEPSS rescore
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 01:59 UTCEPSS rescore
  19. 2026-07-15 01:59 UTCEPSS rescore
  20. 2026-07-13 22:29 UTCEPSS rescore
  21. 2026-07-12 05:45 UTCEPSS rescore
  22. 2026-07-11 08:26 UTCEPSS rescore
  23. 2026-07-09 19:09 UTCEPSS rescore
  24. 2026-07-09 19:09 UTCEPSS rescore
  25. 2026-07-08 15:14 UTCEPSS rescore
Show 70 more
  1. 2026-07-07 13:45 UTCEPSS rescore
  2. 2026-07-07 13:45 UTCEPSS rescore
  3. 2026-07-07 10:51 UTCOSV refresh
  4. 2026-07-06 16:26 UTCEPSS rescore
  5. 2026-07-06 16:26 UTCEPSS rescore
  6. 2026-07-06 02:22 UTCEPSS rescore
  7. 2026-07-05 02:29 UTCEPSS rescore
  8. 2026-07-04 06:30 UTCEPSS rescore
  9. 2026-07-04 06:30 UTCEPSS rescore
  10. 2026-07-01 15:06 UTCEPSS rescore
  11. 2026-06-30 23:21 UTCEPSS rescore
  12. 2026-06-30 23:21 UTCEPSS rescore
  13. 2026-06-29 14:05 UTCEPSS rescore
  14. 2026-06-28 14:07 UTCEPSS rescore
  15. 2026-06-28 04:55 UTCEPSS rescore
  16. 2026-06-28 04:55 UTCEPSS rescore
  17. 2026-06-27 03:08 UTCEPSS rescore
  18. 2026-06-27 03:07 UTCEPSS rescore
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-24 14:04 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
  26. 2026-06-21 14:56 UTCEPSS rescore
  27. 2026-06-21 14:56 UTCEPSS rescore
  28. 2026-06-21 01:59 UTCEPSS rescore
  29. 2026-06-19 19:25 UTCEPSS rescore
  30. 2026-06-19 19:25 UTCEPSS rescore
  31. 2026-06-18 21:44 UTCOSV refresh
  32. 2026-06-18 17:52 UTCEPSS rescore
  33. 2026-06-18 17:52 UTCEPSS rescore
  34. 2026-06-17 17:52 UTCEPSS rescore
  35. 2026-06-16 17:52 UTCEPSS rescore
  36. 2026-06-15 17:48 UTCEPSS rescore
  37. 2026-06-14 23:17 UTCEPSS rescore
  38. 2026-06-13 22:59 UTCEPSS rescore
  39. 2026-06-13 22:59 UTCEPSS rescore
  40. 2026-06-12 23:11 UTCEPSS rescore
  41. 2026-06-12 23:11 UTCEPSS rescore
  42. 2026-06-11 13:59 UTCEPSS rescore
  43. 2026-06-11 13:59 UTCEPSS rescore
  44. 2026-06-10 22:18 UTCEPSS rescore
  45. 2026-06-10 22:18 UTCEPSS rescore
  46. 2026-06-10 13:21 UTCEPSS rescore
  47. 2026-06-08 14:16 UTCEPSS rescore
  48. 2026-06-08 14:16 UTCEPSS rescore
  49. 2026-06-07 15:24 UTCEPSS rescore
  50. 2026-06-07 15:24 UTCEPSS rescore
  51. 2026-06-06 13:46 UTCEPSS rescore
  52. 2026-06-06 13:46 UTCEPSS rescore
  53. 2026-06-05 22:46 UTCEPSS rescore
  54. 2026-06-05 22:46 UTCEPSS rescore
  55. 2026-06-05 06:09 UTCEPSS rescore
  56. 2026-06-05 06:09 UTCEPSS rescore
  57. 2026-06-04 13:11 UTCEPSS rescore
  58. 2026-06-04 13:11 UTCEPSS rescore
  59. 2026-06-02 20:12 UTCEPSS rescore
  60. 2026-06-02 20:12 UTCEPSS rescore
  61. 2026-06-01 13:51 UTCEPSS rescore
  62. 2026-06-01 13:51 UTCEPSS rescore
  63. 2026-06-01 13:51 UTCEPSS rescore
  64. 2026-05-31 22:30 UTCEPSS rescore
  65. 2026-05-31 22:30 UTCEPSS rescore
  66. 2026-05-30 11:33 UTCEG score recompute
  67. 2026-05-30 11:33 UTCVendor advisory
  68. 2026-05-30 11:33 UTCGHSA enrichment
  69. 2026-05-29 19:50 UTCOSV refresh
  70. 2026-05-29 13:43 UTCEPSS rescore

Frequently asked(5)

What is CVE-2024-56171?
CVE-2024-56171 is a high vulnerability published on February 18, 2025. libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a use-after-free in xmlSchemaIDCFillNodeTables and xmlSchemaBubbleIDCNodeTables in xmlschemas.c. To exploit this, a crafted XML document must be validated against an XML schema with certain identity constraints, or a crafted XML schema must be…
When was CVE-2024-56171 disclosed?
CVE-2024-56171 was first published in the National Vulnerability Database on February 18, 2025, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-56171 actively exploited?
CVE-2024-56171 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 36.8% of all scored CVEs.
What is the CVSS score of CVE-2024-56171?
CVE-2024-56171 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-56171?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-56171, 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-2024-56171

Explore →

Is Your Infrastructure Affected by CVE-2024-56171?

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

Start Free Scan →Browse All CVEs