CVE-2026-0989

LOWPre-NVD 3.73.7—
EchelonGraph scoreMEDIUM confidence

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-01-15. a secondary CVSS source baseline 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.7Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was identified in the RelaxNG parser of libxml2 related to how external schema inclusions are handled. The parser does not enforce a limit on inclusion depth when resolving nested directives. Specially crafted or overly complex schemas can cause excessive recursion during parsing. This may lead to stack exhaustion and application crashes, creating a denial-of-service risk.

CVSS v3
3.7
EG Score
3.7(medium)
EG Risk
17(Track)
EG Risk 17/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
Severity37% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

January 15, 2026

Last Modified

September 1, 2026

References (4)

Vendor Advisories for CVE-2026-0989(2)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython-libxml2 (2.9.1+dfsg1-3ubuntu4.13+esm11) @ trusty2026-09-01ubuntu
redhatlibxml2-main-2.15.2-0.3.hum12026-04-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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libxml22.9.10+dfsg-6.7 ... 2.9.10+dfsg-6.7+deb11u9 (10 versions)2.9.10+dfsg-6.7+deb11u10—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libxml22.9.14+dfsg-1.2 ... 2.9.14+dfsg-1.3~deb12u5 (6 versions)2.9.14+dfsg-1.3~deb12u6—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libxml22.12.7+dfsg+really2.9.14-2.1, 2.12.7+dfsg+really2.9.14-2.1+deb13u1, 2.12.7+dfsg+really2.9.14-2.1+deb13u22.12.7+dfsg+really2.9.14-2.1+deb13u3—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libxml22.12.7+dfsg+really2.9.14-2.1 ... 2.15.1+dfsg-2 (25 versions)2.15.2+dfsg-0.1—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 15× 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.

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

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

Frequently asked(5)

What is CVE-2026-0989?
CVE-2026-0989 is a low vulnerability published on January 15, 2026. A flaw was identified in the RelaxNG parser of libxml2 related to how external schema inclusions are handled. The parser does not enforce a limit on inclusion depth when resolving nested <include> directives. Specially crafted or overly complex schemas can cause excessive recursion during parsing.…
When was CVE-2026-0989 disclosed?
CVE-2026-0989 was first published in the National Vulnerability Database on January 15, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0989 actively exploited?
CVE-2026-0989 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 61.4% of all scored CVEs.
What is the CVSS score of CVE-2026-0989?
CVE-2026-0989 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-0989?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0989, 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-2026-0989

Explore →

Is Your Infrastructure Affected by CVE-2026-0989?

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

Start Free Scan →Browse All CVEs