CVE-2026-86137

MEDIUMNVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 97% 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
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.1Exploit: None knownExposed: 0

A fix is available — apply it.

In libxml2 before 2.15.4, xmlFAParsePosCharGroup has an out-of-bounds read, aka an out-of-bounds read in the NXT macro in xmlregexp.

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

Published

September 5, 2026

Last Modified

September 15, 2026

Advisory Details (3)

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

Out-of-bounds read in xmlFAParsePosCharGroup (#1099) · Issues · GNOME / libxml2 · GitLab

https://gitlab.gnome.org/GNOME/libxml2/-/work_items/1099
generic

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

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

commit 76fe08d97de8 (GNOME/libxml2)

Fix landed in GNOME/libxml2 commit 76fe08d97de8 — awaiting tagged release

https://github.com/GNOME/libxml2/commit/76fe08d97de88bfaef2f7d5cd27f11954cc5bee2

Vendor Advisories for CVE-2026-86137(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 24× 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-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 14:17 UTCEG score recompute
  3. 2026-09-18 14:17 UTCVendor advisory
  4. 2026-09-18 14:17 UTCGHSA enrichment
  5. 2026-09-17 19:32 UTCEPSS rescore
  6. 2026-09-17 16:16 UTCVendor advisory
  7. 2026-09-17 16:16 UTCGHSA enrichment
  8. 2026-09-16 18:22 UTCEG score recompute
  9. 2026-09-16 18:22 UTCVendor advisory
  10. 2026-09-16 18:22 UTCGHSA enrichment
  11. 2026-09-16 14:09 UTCEPSS rescore
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-15 19:52 UTCEG score recompute▲ 3.20
  14. 2026-09-15 19:52 UTCVendor advisory
  15. 2026-09-15 19:52 UTCGHSA enrichment
  16. 2026-09-15 19:52 UTCNVD updateCVSS v3 → 6.1 · severity → MEDIUM
  17. 2026-09-15 03:12 UTCEPSS rescore
  18. 2026-09-15 03:12 UTCEPSS rescore
  19. 2026-09-14 14:32 UTCEG score recompute
  20. 2026-09-14 14:32 UTCVendor advisory
  21. 2026-09-14 14:32 UTCGHSA enrichment
  22. 2026-09-14 14:00 UTCEG score recompute
  23. 2026-09-14 14:00 UTCVendor advisory
  24. 2026-09-14 14:00 UTCGHSA enrichment
  25. 2026-09-12 03:08 UTCEG score recompute
Show 16 more
  1. 2026-09-12 03:08 UTCVendor advisory
  2. 2026-09-12 03:08 UTCGHSA enrichment
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-08 22:01 UTCEPSS rescore
  6. 2026-09-08 21:54 UTCVendor advisory
  7. 2026-09-08 21:53 UTCGHSA enrichment
  8. 2026-09-08 10:47 UTCEG score recompute
  9. 2026-09-08 10:47 UTCVendor advisory
  10. 2026-09-08 10:47 UTCGHSA enrichment
  11. 2026-09-08 10:44 UTCGHSA enrichment
  12. 2026-09-06 13:48 UTCEPSS rescore
  13. 2026-09-05 15:31 UTCEPSS rescore
  14. 2026-09-05 05:23 UTCEG score recompute
  15. 2026-09-05 04:24 UTCEG score recompute
  16. 2026-09-05 04:23 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-86137?
CVE-2026-86137 is a medium vulnerability published on September 5, 2026. In libxml2 before 2.15.4, xmlFAParsePosCharGroup has an out-of-bounds read, aka an out-of-bounds read in the NXT macro in xmlregexp.
When was CVE-2026-86137 disclosed?
CVE-2026-86137 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-86137 actively exploited?
CVE-2026-86137 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 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-86137?
CVE-2026-86137 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-86137?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86137, 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-86137

Explore →

Is Your Infrastructure Affected by CVE-2026-86137?

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

Start Free Scan →Browse All CVEs