CVE-2026-34481

High

Description

Apache Log4j's JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records. An attacker can exploit this issue only if both of the following conditions are met: * The application uses JsonTemplateLayout. * The application logs a MapMessage, or logs an object directly (e.g., via Logger.info(Object), which wraps it in an ObjectMessage), where the message contains an attacker-controlled floating-point value. Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue. Note: The fix released in version 2.25.4 did not cover all affected code paths. CVE-2026-49844 was assigned to the remaining issue, which concerns the MapMessage.asJson() serialization in Apache Log4j API and is fixed in versions 2.25.5 and 2.26.1.

SeverityHigh
CVSS7.5
Exploit probability53. percentile0.7%
ProductApache Log4j
PublishedApr 10, 2026
First seenApr 10, 2026
Weakness typeCWE-116CWE-116

How to fix

Update
  • apache log4j2.25.4 or later
  • org.apache.logging.log4j:log4j-layout-template-json2.25.4 or later

Affected products

ProductAffected versionsFixed in
apache log4j2.14.0 ≤ v < 2.25.4, 3.0.02.25.4
org.apache.logging.log4j:log4j-layout-template-jsonMaven2.14.0 ≤ v < 2.25.4, 3.0.0-alpha1 ≤ v ≤ 3.0.0-beta32.25.4

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.