Loading vulnerability…
CVE-2023-39615 is a disputed libxml2 issue reported in version 2.11.0 involving an alleged out-of-bounds read in xmlSAX2StartElement(). The reported condition was said to be reachable using crafted XML and capable of crashing an application. The libxml2 vendor stated that the scenario depends on the unsupported legacy SAX1 interface with custom callbacks, and that the observed crash occurs independently of crafted input under that unsupported configuration. Some downstream advisories characterize the issue as a global buffer overflow, but the available technical description identifies an out-of-bounds read.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
23 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability listed as addressed by the updated image; no technical details are provided in this advisory.
Addressed in updated multicluster engine for Kubernetes images; flaw details are not supplied.
Unknown
A vulnerability addressed by this security update; no technical details are provided.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.