CVE-2025-24855

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

A fix is available — apply it.

numbers.c in libxslt before 1.1.43 has a use-after-free because, in nested XPath evaluations, an XPath context node can be modified but never restored. This is related to xsltNumberFormatGetValue, xsltEvalXPathPredicate, xsltEvalXPathStringNs, and xsltComputeSortResultInternal.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
24.3%
KEV
Not listed

Published

March 14, 2025

Last Modified

November 3, 2025

Patch Availability(20)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuxsltproc (1.1.34-4ubuntu0.20.04.3) @ focal2026-05-30ubuntu
ubuntuxsltproc (1.1.28-2.1ubuntu0.3+esm3) @ xenial2026-05-30ubuntu
redhatrhcos-412.86.202505281830-02025-06-05redhat
redhatrhcos-414.92.202505141057-02025-05-21redhat
redhatrhcos-416.94.202505051351-02025-05-15redhat
redhatrhcos-413.92.202505061702-02025-05-15redhat
redhatlibxslt-0:1.1.39-7.el10_02025-05-13redhat
redhatrhcos-417.94.202504291434-02025-05-09redhat
redhatrhcos-418.94.202504291430-02025-05-09redhat
redhatrhcos-415.92.202504282058-02025-05-08redhat
redhatlibxslt-0:1.1.28-9.el7_92025-04-23redhat
redhatlibxslt-0:1.1.32-8.el8_82025-04-07redhat
redhatlibxslt-0:1.1.32-8.el8_62025-04-07redhat
redhatlibxslt-0:1.1.34-11.el9_02025-04-07redhat
redhatlibxslt-0:1.1.32-8.el8_42025-04-07redhat
redhatlibxslt-0:1.1.32-6.1.el8_102025-04-07redhat
redhatlibxslt-0:1.1.32-6.el8_22025-04-07redhat
redhatlibxslt-0:1.1.34-10.el9_22025-04-02redhat
redhatlibxslt-0:1.1.34-10.el9_42025-03-31redhat
redhatlibxslt-0:1.1.34-9.el9_5.12025-03-24redhat

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

(15)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2025-24855?
CVE-2025-24855 is a high vulnerability published on March 14, 2025. numbers.c in libxslt before 1.1.43 has a use-after-free because, in nested XPath evaluations, an XPath context node can be modified but never restored. This is related to xsltNumberFormatGetValue, xsltEvalXPathPredicate, xsltEvalXPathStringNs, and xsltComputeSortResultInternal.
When was CVE-2025-24855 disclosed?
CVE-2025-24855 was first published in the National Vulnerability Database on March 14, 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-2025-24855 actively exploited?
CVE-2025-24855 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-24855?
CVE-2025-24855 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-24855?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-24855, 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-2025-24855

Explore →

Is Your Infrastructure Affected by CVE-2025-24855?

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