CVE-2025-9714

MEDIUMNVD 5.56.2
EchelonGraph scoreMEDIUM confidence

Score 6.2 from GitHub Security Advisory published 2025-09-10. NVD baseline CVSS 6.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

A fix is available — apply it.

Uncontrolled recursion in XPath evaluation in libxml2 up to and including version 2.9.14 allows a local attacker to cause a stack overflow via crafted expressions. XPath processing functions xmlXPathRunEval, xmlXPathCtxtCompile, and xmlXPathEvalExpr were resetting recursion depth to zero before making potentially recursive calls. When such functions were called recursively this could allow for uncontrolled recursion and lead to a stack overflow. These functions now preserve recursion depth across recursive calls, allowing recursion depth to be controlled.

CVSS v3
5.5
EG Score
6.2(medium)
EPSS
4.1%
KEV
Not listed

Published

September 10, 2025

Last Modified

June 17, 2026

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatlibxml2-0:2.9.7-13.el8_6.132026-05-11redhat
redhatlibxml2-0:2.9.7-16.el8_8.132026-05-07redhat
redhatlibxml2-0:2.9.7-9.el8_4.92026-05-07redhat
redhatlibxml2-0:2.9.7-21.el8_10.42026-04-28redhat
redhatlibxml2-main-2.15.2-0.3.hum12026-04-10redhat
redhatrhaiis/vllm-cuda-rhel9:17721605932026-02-27redhat
redhatrhaiis/vllm-rocm-rhel9:17721606252026-02-27redhat
redhatrhcos-415.92.202601271320-02026-02-05redhat
redhatrhcos-4.19.9.6.202601260820-02026-02-04redhat
redhatrhcos-418.94.202601202224-02026-02-03redhat
redhatrhceph/rhceph-8-rhel9:17695123832026-02-02redhat
redhatrhcos-414.92.202601191325-02026-01-30redhat
redhatrhcos-416.94.202601160124-02026-01-30redhat
redhatrhcos-4.20.9.6.202601211057-02026-01-27redhat
redhatrhcos-417.94.202601120213-02026-01-22redhat
redhatrhcos-413.92.202601130113-02026-01-22redhat
redhatdiscovery/discovery-ui-rhel9:17679045732026-01-08redhat
redhatrhaiis/vllm-rocm-rhel9:3.2.5-17655526032025-12-17redhat
redhatrhceph/rhceph-7-rhel9:72025-12-16redhat
redhatrhceph/rhceph-8-rhel9:82025-12-16redhat
redhatrhaiis/vllm-cuda-rhel9:3.2.5-17655525802025-12-15redhat
redhatrhaiis/model-opt-cuda-rhel9:3.2.5-17653611842025-12-15redhat
redhatrhaiis/vllm-tpu-rhel9:3.2.5-17655526192025-12-15redhat
redhatrhaiis/vllm-rocm-rhel9:3.2.5-17653611802025-12-15redhat
redhatinsights-proxy/insights-proxy-container-rhel9:1.5.9-17652018562025-12-08redhat
redhatlibxml2-0:2.9.13-14.el9_72025-12-01redhat
redhatlibxml2-0:2.9.13-12.el9_6.12025-12-01redhat
redhatlibxml2-0:2.9.13-13.el9_42025-11-26redhat
redhatlibxml2-0:2.9.13-3.el9_2.102025-11-26redhat
redhatlibxml2-0:2.9.13-1.el9_0.82025-11-26redhat

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

(12)

Data Freshness Timeline

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

Showing the most recent 100 of 101 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-9714?
CVE-2025-9714 is a medium vulnerability published on September 10, 2025. Uncontrolled recursion in XPath evaluation in libxml2 up to and including version 2.9.14 allows a local attacker to cause a stack overflow via crafted expressions. XPath processing functions xmlXPathRunEval, xmlXPathCtxtCompile, and xmlXPathEvalExpr were resetting recursion depth to zero before…
When was CVE-2025-9714 disclosed?
CVE-2025-9714 was first published in the National Vulnerability Database on September 10, 2025, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-9714 actively exploited?
CVE-2025-9714 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-9714?
CVE-2025-9714 has a CVSS v3 base score of 5.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 6.2.
How do I remediate CVE-2025-9714?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-9714, 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-9714

Explore →

Is Your Infrastructure Affected by CVE-2025-9714?

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