Loading vulnerability…
Apache Log4j JsonTemplateLayout, in versions up to and including 2.25.3, improperly serializes non-finite floating-point values such as NaN, Infinity, and -Infinity when they appear in logged event data. Because these tokens are not valid JSON under RFC 8259, the layout can emit malformed JSON records. The issue is reachable when an application uses JsonTemplateLayout and logs a MapMessage or directly logs an object that is wrapped as an ObjectMessage, where the logged content contains an attacker-controlled non-finite floating-point value. The flaw affects JSON output correctness rather than memory safety or direct code execution, but it can break systems that rely on strict JSON parsing of log streams.
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.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.