CVE-2026-86140Disclosure(xmlsoft / libxml2)

LOWCVSS 7.8 · HIGH

Signal is active with 2 mentions in latest observed window

Immediate actions

  • Patch xmlsoft libxml2 systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

In libxml2 before 2.15.4, xmlSnprintfElements in valid.c has a strcat stack-based buffer overflow.

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-121

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • libxml2

Threat summary

  • Patch or workaround signal is available
  • 2 mentions across 1 observed day

What's happening

  • Patch or workaround mentioned in 2 signals
  • Technical details provided in 2 signals
  • Disclosure: 1 classified signal
  • 2 total mentions across 1 day

Affected systems

Vendors
Products
libxml2

Deep dive

Activity timeline2 mentions / 1d
01122Mentions · 2026-09-05: 2Patch / Workaround · 2026-09-05: 2Technical Details · 2026-09-05: 209-05
Signal classification2 categories
Disclosure
150.0%
Patch
150.0%
Full discourse2 posts
  • CyberSignal | Cybersecurity & AI News@XQOPTRX
    Disclosure

    ⚠️ NEW VULNERABILITY DISCLOSURE — EIGHT CVEs were published today for libxml2, including a CVSS 8.0 stack-based buffer overflow. All eight affect libxml2 versions before 2.15.4. CyberSignal Priority: 🟠 HIGH CVE range: CVE-2026-86137 → CVE-2026-86144 Highest severity: CVE-2026-86140 — CVSS 8.0 Affected: libxml2 < 2.15.4 Fixed upstream: 2.15.4 Active exploitation: NOT CONFIRMED 🔎 What was disclosed The September 5 batch includes multiple memory-safety and integer-handling problems: • CVE-2026-86140 — stack-based buffer overflow in xmlSnprintfElements — CVSS 8.0 • CVE-2026-86138 — integer overflow resulting in a heap-based buffer overflow • CVE-2026-86139 — integer overflow in xmlURIEscapeStr • CVE-2026-86142 — heap-based buffer overflow involving XPointer processing • CVE-2026-86143 — integer-handling flaw allowing negative lengths to reach write callbacks • CVE-2026-86144 — XInclude processing fails to propagate parseFlags The last issue is particularly interesting because it can undermine protections involving XML_PARSE_NONET. In configurations using a custom resource loader, the CVE record says this could contribute to: XXE SSRF or denial of service. Other bugs in the batch include an out-of-bounds read and a NULL-pointer dereference. 🎯 Why this matters libxml2 is not simply another standalone application. It is a foundational XML parsing library embedded across software stacks, operating systems, libraries, appliances and enterprise applications. That means organizations may depend on it without seeing “libxml2” prominently in their normal application inventory. 🛡️ Defender action Inventory software and containers that embed libxml2. For directly managed deployments, move to a vendor-supported build containing the 2.15.4 fixes. Linux distributions may backport security fixes without changing to the exact upstream version, so follow your distribution's security advisory rather than replacing system libraries manually. There is currently NO CONFIRMED ACTIVE EXPLOITATION from the sources reviewed. 🧠 CyberSignal Insight The most important number here may not be CVSS 8.0. It is: 8 vulnerabilities ↓ 1 foundational parser ↓ potentially thousands of downstream products. Dependency reach can turn a moderate-looking library disclosure into a much larger patch-management problem. Sources: MITRE/CVE · GNOME/libxml2 · CIRCL Vulnerability-Lookup · NVD

    Post summary

    Eight new libxml2 CVEs, including a stack‑based buffer overflow, were disclosed with technical details and patch guidance, and no active exploitation or PoC has been reported.

    01010113
    197 followersView on X
  • Upwind Security MDR@UpwindMDR
    Patch

    🚨HIGH - libxml2 Stack Buffer Overflow in xmlSnprintfElements (CVE-2026-86140) libxml2 valid.c:xmlSnprintfElements() uses strcat() to build element strings into a fixed-size stack buffer; attacker-controlled XML can trigger the validation path and overflow the stack, causing memory corruption and potential RCE/DoS. Not affected if the validation code path isn’t reached. 👉Affected: libxml2 < 2.15.4 | Upgrade to 2.15.4

    Post summary

    An advisory for a critical stack buffer overflow in libxml2’s xmlSnprintfElements function, allowing RCE/DoS via malformed XML, mitigated by upgrading to libxml2 version 2.15.4.

    00000104
    303 followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appxmlsoftlibxml2---

Explore more