CVE-2026-86144

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 93% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 5 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: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

In xinclude in libxml2 before 2.15.4, xmlXIncludeProcess and xmlXIncludeProcessTree do not propagate parseFlags. This has security relevance for, for example, the XML_PARSE_NONET flag, if (without it) a custom resource loader accesses the internet and triggers XML external entity injection, SSRF, or a denial of service (e.g., for an attacker-controlled internet resource that is intentionally slow).

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

Published

September 5, 2026

Last Modified

September 15, 2026

Advisory Details (2)

Auto-updated Sep 5, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit b63cd517afec (GNOME/libxml2)

Fix landed in GNOME/libxml2 commit b63cd517afec — awaiting tagged release

https://github.com/GNOME/libxml2/commit/b63cd517afecb76582dd9488c55e54ceaf50de61
generic

Comparing v2.15.3...v2.15.4 · GNOME/libxml2 · GitHub

https://github.com/GNOME/libxml2/compare/v2.15.3...v2.15.4

Vendor Advisories for CVE-2026-86144(3)

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.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libxml22.12.3+dfsg-0exp1 ... 2.9.14+dfsg-1.3~deb12u6 (49 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libxml22.12.7+dfsg+really2.9.14-2.1 ... 2.15.4+dfsg-1 (31 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libxml22.12.7+dfsg+really2.9.14-2.1 ... 2.15.4+dfsg-1 (28 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 37× in last 7d / 68× 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-18 22:05 UTCEG score recompute
  2. 2026-09-18 22:05 UTCVendor advisory
  3. 2026-09-18 22:04 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 09:53 UTCVendor advisory
  6. 2026-09-18 09:53 UTCGHSA enrichment
  7. 2026-09-17 21:42 UTCEG score recompute
  8. 2026-09-17 21:42 UTCVendor advisory
  9. 2026-09-17 21:42 UTCGHSA enrichment
  10. 2026-09-17 19:32 UTCEPSS rescore
  11. 2026-09-17 09:30 UTCVendor advisory
  12. 2026-09-17 09:30 UTCGHSA enrichment
  13. 2026-09-16 21:19 UTCEG score recompute
  14. 2026-09-16 21:19 UTCVendor advisory
  15. 2026-09-16 21:19 UTCGHSA enrichment
  16. 2026-09-16 14:09 UTCEPSS rescore
  17. 2026-09-16 09:00 UTCEG score recompute
  18. 2026-09-16 09:00 UTCVendor advisory
  19. 2026-09-16 09:00 UTCGHSA enrichment
  20. 2026-09-16 05:15 UTCEPSS rescore
  21. 2026-09-15 19:40 UTCEG score recompute▲ 2.20
  22. 2026-09-15 19:40 UTCVendor advisory
  23. 2026-09-15 19:40 UTCGHSA enrichment
  24. 2026-09-15 19:32 UTCNVD updateCVSS v3 → 7.8 · severity → HIGH
  25. 2026-09-15 06:38 UTCEG score recompute
Show 43 more
  1. 2026-09-15 06:38 UTCVendor advisory
  2. 2026-09-15 06:38 UTCGHSA enrichment
  3. 2026-09-15 03:12 UTCEPSS rescore
  4. 2026-09-15 03:12 UTCEPSS rescore
  5. 2026-09-14 08:48 UTCEG score recompute
  6. 2026-09-14 08:48 UTCVendor advisory
  7. 2026-09-14 08:48 UTCGHSA enrichment
  8. 2026-09-13 10:59 UTCEG score recompute
  9. 2026-09-13 10:59 UTCVendor advisory
  10. 2026-09-13 10:59 UTCGHSA enrichment
  11. 2026-09-12 13:10 UTCVendor advisory
  12. 2026-09-12 13:10 UTCGHSA enrichment
  13. 2026-09-11 15:21 UTCEG score recompute
  14. 2026-09-11 15:21 UTCVendor advisory
  15. 2026-09-11 15:21 UTCGHSA enrichment
  16. 2026-09-11 14:53 UTCEPSS rescore
  17. 2026-09-11 14:53 UTCEPSS rescore
  18. 2026-09-10 17:32 UTCEG score recompute
  19. 2026-09-10 17:32 UTCVendor advisory
  20. 2026-09-10 17:32 UTCGHSA enrichment
  21. 2026-09-09 19:43 UTCEG score recompute
  22. 2026-09-09 19:43 UTCVendor advisory
  23. 2026-09-09 19:43 UTCGHSA enrichment
  24. 2026-09-08 22:01 UTCEPSS rescore
  25. 2026-09-08 21:54 UTCVendor advisory
  26. 2026-09-08 21:53 UTCGHSA enrichment
  27. 2026-09-08 15:13 UTCEG score recompute
  28. 2026-09-08 15:13 UTCVendor advisory
  29. 2026-09-08 15:13 UTCGHSA enrichment
  30. 2026-09-08 14:17 UTCEG score recompute
  31. 2026-09-08 14:17 UTCVendor advisory
  32. 2026-09-08 14:16 UTCGHSA enrichment
  33. 2026-09-07 22:53 UTCEG score recompute
  34. 2026-09-07 22:53 UTCGHSA enrichment
  35. 2026-09-07 01:03 UTCEG score recompute
  36. 2026-09-07 01:03 UTCGHSA enrichment
  37. 2026-09-06 13:48 UTCEPSS rescore
  38. 2026-09-06 03:12 UTCEG score recompute
  39. 2026-09-06 03:12 UTCGHSA enrichment
  40. 2026-09-05 15:31 UTCEPSS rescore
  41. 2026-09-05 05:23 UTCEG score recompute
  42. 2026-09-05 04:44 UTCEG score recompute
  43. 2026-09-05 04:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-86144?
CVE-2026-86144 is a high vulnerability published on September 5, 2026. In xinclude in libxml2 before 2.15.4, xmlXIncludeProcess and xmlXIncludeProcessTree do not propagate parseFlags. This has security relevance for, for example, the XMLPARSENONET flag, if (without it) a custom resource loader accesses the internet and triggers XML external entity injection, SSRF, or…
When was CVE-2026-86144 disclosed?
CVE-2026-86144 was first published in the National Vulnerability Database on September 5, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-86144 actively exploited?
CVE-2026-86144 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 92.5% of all scored CVEs.
What is the CVSS score of CVE-2026-86144?
CVE-2026-86144 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-86144?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86144, 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-86144

Explore →

Is Your Infrastructure Affected by CVE-2026-86144?

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

Start Free Scan →Browse All CVEs