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 containing an attacker-controlled floating-point value.


Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.

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.

{"timestamp":"2026-04-10T17:41:23.224802Z","id":"CVE-2026-34481","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}

[{"vendor":"Apache Software Foundation","product":"Apache Log4j JSON Template Layout","defaultStatus":"unaffected","collectionURL":"https://repo.maven.apache.org/maven2","packageName":"org.apache.logging.log4j:log4j-layout-template-json","cpes":["cpe:2.3:a:apache:log4j_layout_template_json:*:*:*:*:*:*:*:*"],"packageURL":"pkg:maven/org.apache.logging.log4j/log4j-layout-template-json","versions":[{"version":"2.14.0","lessThan":"2.25.4","versionType":"maven","status":"affected"},{"version":"3.0.0-alpha1","lessThanOrEqual":"3.0.0-beta3","versionType":"maven","status":"affected"}]}]

AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

OR
          *cpe:2.3:a:apache:log4j:*:*:*:*:*:*:*:* versions from (including) 2.14.0 up to (excluding) 2.25.4
          *cpe:2.3:a:apache:log4j:3.0.0:alpha1:*:*:*:*:*:*
          *cpe:2.3:a:apache:log4j:3.0.0:alpha1_rc1:*:*:*:*:*:*
          *cpe:2.3:a:apache:log4j:3.0.0:alpha1_rc2:*:*:*:*:*:*
          *cpe:2.3:a:apache:log4j:3.0.0:beta1:*:*:*:*:*:*
          *cpe:2.3:a:apache:log4j:3.0.0:beta2:*:*:*:*:*:*
          *cpe:2.3:a:apache:log4j:3.0.0:beta3:*:*:*:*:*:*

Apache Software Foundation: https://github.com/apache/logging-log4j2/pull/4080 Types: Issue Tracking

Apache Software Foundation: https://lists.apache.org/thread/n34zdv00gbkdbzt2rx9rf5mqz6lhopcv Types: Mailing List, Vendor Advisory

Apache Software Foundation: https://logging.apache.org/cyclonedx/vdr.xml Types: Product

Apache Software Foundation: https://logging.apache.org/log4j/2.x/manual/json-template-layout.html Types: Technical Description

Apache Software Foundation: https://logging.apache.org/security.html#CVE-2026-34481 Types: Vendor Advisory

CVE: http://www.openwall.com/lists/oss-security/2026/04/10/10 Types: Mailing List, Third Party Advisory

http://www.openwall.com/lists/oss-security/2026/04/10/10

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 containing an attacker-controlled floating-point value.


Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.

AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

CWE-116

https://github.com/apache/logging-log4j2/pull/4080

https://lists.apache.org/thread/n34zdv00gbkdbzt2rx9rf5mqz6lhopcv

https://logging.apache.org/cyclonedx/vdr.xml

https://logging.apache.org/log4j/2.x/manual/json-template-layout.html

https://logging.apache.org/security.html#CVE-2026-34481