CVE-2026-34480 is an output-neutralization flaw in Apache Log4j Core affecting XmlLayout in versions up to and including 2.25.3. When a log message or mapped diagnostic context value contains characters forbidden by the XML 1.0 specification, XmlLayout fails to sanitize those characters before serializing the event as XML. This can produce invalid XML output or trigger failures during log serialization, depending on the StAX implementation used by the runtime. With the JRE built-in StAX implementation, forbidden characters are written into the output stream, resulting in malformed XML documents. With alternative StAX implementations such as Woodstox, the logging operation can raise an exception and the event is not delivered to the intended appender, instead only being reported through Log4j's internal status logger.
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 valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability in Oracle Communications addressed as part of a consolidated fix bundled with CVE-2026-34481.
A high-severity vulnerability affecting HPE Telco Universal SLA Management 4.6 and earlier, associated with potential denial of service and/or CRLF injection impact according to the bulletin.
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.