Heap-based Buffer Overflow in Apache HTTP Server mod_xml2enc
CVE-2026-42536 is a low-severity heap-based buffer overflow in Apache HTTP Server affecting versions 2.4.0 through 2.4.67. The issue occurs in deployments using mod_xml2enc and involves xml2StartParse when processing untrusted content. Apache identified the flaw as a heap overflow in mod_xml2enc via xml2StartParse and fixed it in the 2.4.x branch in revision r1934971, released in Apache HTTP Server 2.4.68. The available information does not include deeper root-cause details such as the exact faulty bounds calculation or specific vulnerable code path beyond the xml2StartParse/mod_xml2enc handling of untrusted input.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A heap overflow vulnerability in Apache HTTP Server mod_xml2enc via xml2StartParse with untrusted content.
Apache HTTP Server vulnerability affecting mod_xml2enc, fixed in version 2.4.68.
Apache HTTP Server vulnerability in mod_xml2enc.
A heap-based buffer overflow vulnerability in Apache HTTP Server involving mod_xml2enc and xml2StartParse when processing untrusted content.
The version that knows your environment.
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.