CVE-2026-34481 Apache Log4j JSON Template Layout: Improper serialization of non-finite floating-point values in JsonTemplateLayout

Medium 6.3 Published Updated

Attackers can cause log processing failures by injecting non-finite floating-point values into logs using JsonTemplateLayout, requiring an upgrade to Log4j.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-34481?

CVE-2026-34481 is a medium-severity vulnerability in Apache Log4j JSON Template Layout, published on 10 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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.

Weakness: CWE-116

Which versions are affected by CVE-2026-34481?

4 open source packages ship an affected version, including org.apache.logging.log4j:log4j-layout-template-json. It affects 1 product.

PackageAffectedFixed in
org.apache.logging.log4j:log4j-layout-template-json MavenFrom 2.14.02.25.4
org.apache.logging.log4j:log4j-layout-template-json MavenFrom 2.14.02.25.4
org.apache.logging.log4j:log4j-layout-template-json MavenFrom 3.0.0-alpha1 to 3.0.0-beta3None
org.apache.logging.log4j:log4j-layout-template-json MavenFrom 3.0.0-alpha1 to 3.0.0-beta3None

Products include Apache Log4j.

How do I fix CVE-2026-34481?

Upgrade org.apache.logging.log4j:log4j-layout-template-json to 2.25.4 or later.

Is CVE-2026-34481 being exploited?

There is no known exploitation of CVE-2026-34481 in the wild and no public exploit code.

Sources

Also known as CLEANSTART-2026-CS40307, CLEANSTART-2026-NV45884, CLEANSTART-2026-QA30361, CLEANSTART-2026-RV51042, CLEANSTART-2026-SX30440, CLSA-2026-1784769579 and 27 more.

Is CVE-2026-34481 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free