A flaw was found in libxml2 with Python bindings enabled. A remote attacker could exploit this vulnerability by providing a specially crafted XML document containing a Document Type Definition (DTD) with enumerated attribute values. This triggers a double-free error in the SAX attributeDecl callback handler, where a string is freed twice. This flaw can lead to a denial of service (DoS) due to a reproducible crash in Python applications using the libxml2 SAX bindings.
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-74860 is a critical memory safety vulnerability in libxml2's Python bindings that exploits improper memory management in the SAX (Simple API for XML) parser. When processing specially crafted XML documents containing Document Type Definitions (DTDs) with enumerated attribute values, the attributeDecl callback handler attempts to free the same memory region twice, triggering a double-free condition. This vulnerability affects any Python application that uses libxml2's SAX bindings to parse untrusted XML input, including web services, document processors, data parsers, and API gateways. The impact is significant: attackers can reliably crash vulnerable applications with minimal effort, enabling denial of service attacks that disrupt availability and business continuity.
While this CVE lacks direct MITRE ATT&CK mappings, Casky's 754 security skills enable detection of the exploitation patterns through behavioral analysis. Practitioners would leverage skills mapping to Resource Hijacking and Availability-focused attacks, identifying XML parsing anomalies, memory corruption indicators, and process crash patterns. Casky's Claude-powered analysis would correlate suspicious indicators such as: unexpected SAX parser invocation sequences with malformed DTD structures, abnormal memory allocation patterns preceding crashes, and application termination following XML document processing. Security teams using Casky would observe findings flagging untrusted XML input sources, missing input validation controls, and libxml2 version exposure—enabling proactive patching and input sanitization controls before exploitation occurs.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-74860. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation