libxml2 is a widely used XML parser; a stack overflow allowing remote code execution in many apps/services is broadly impactful and warrants org-wide attention.
CVE-2026-86140
Stack-based buffer overflow in libxml2 (xmlSnprintfElements) leading to possible RCE.
Is CVE-2026-86140 being exploited?
Not confirmed. CVE-2026-86140 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.15% probability of exploitation in the next 30 days.
How severe is CVE-2026-86140?
CVE-2026-86140 is rated High with a CVSS score of 8.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-86140?
Yes. A fix has been recorded for CVE-2026-86140. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-86140 affect?
CVE-2026-86140 affects libxml2 < 2.15.4, Linux distributions packaging libxml2, Applications linking libxml2 (XML processors, desktop apps, servers). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-86140?
Upgrade libxml2 to >= 2.15.4 and rebuild dependent packages.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Stack-based buffer overflow via strcat in xmlSnprintfElements can crash or allow remote code execution when parsing crafted XML.
Patch when possible
- affected< 2.15.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.