Quick answers
- Is CVE-2026-74860 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-74860 being exploited in the wild.
- How severe is CVE-2026-74860?
- High severity, with a CVSS score of 8.5, published 8 September 2026.
- Which products and versions are affected?
- libxml2 Project libxml2 <UNKNOWN>.
- Is there a fix for CVE-2026-74860?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-74860 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-74860?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A double-free vulnerability exists in the SAX attributeDecl callback handler in libxml2 when Python bindings are enabled. An attacker can craft an XML document containing a DTD with enumerated attribute values that triggers the vulnerable code path. The memory corruption leads to a reproducible crash in Python applications using libxml2 SAX bindings. The vulnerability is remotely exploitable via network delivery of a malicious XML document and requires no authentication or special privileges. An attacker can achieve denial of service by crashing Python processes that parse untrusted XML input.
Affected products
- libxml2 Project libxml2 <UNKNOWN>
Timeline
- 2026-09-08: disclosed