What is CVE-2026-86144?
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).
The record classifies CVE-2026-86144 under weakness class CWE-669. Its CVSS v3 base vector states that the flaw requires local access to the host, needs no prior authentication, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 75 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 5.6 — MEDIUM
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L - EPSS (FIRST)
- 0.1% probability of exploitation in the next 30 days, higher than 8.3% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 3.1/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-09-05
Is CVE-2026-86144 being exploited?
No public exploitation evidence for CVE-2026-86144 is recorded in the sources Threadlinqs tracks — CISA KEV, Exploit-DB, public proof-of-concept repositories and ProjectDiscovery Nuclei — as of 2026-11-17. That is an absence of evidence in those feeds, not a guarantee that the vulnerability is unexploited.
Affected products and versions
- xmlsoft: libxml2
How to fix CVE-2026-86144
The record marks a vendor fix as available for CVE-2026-86144. Patch reference: https://github.com/GNOME/libxml2/commit/b63cd517afecb76582dd9488c55e54ceaf50de61. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.
Threat activity tracking CVE-2026-86144
1 tracked threat in the Threadlinqs corpus references CVE-2026-86144, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. This product uses the NVD API but is not endorsed or certified by the NVD.