CVE-2026-34481

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

Published Apr 10, 2026 CVSS 4.0 · 6.3 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Apache Log4j’s JsonTemplateLayout, in versions up to 2.25.3, serializes non‑finite floating‑point values such as NaN, Infinity, or –Infinity into JSON. Because those values are prohibited by RFC 8259, the resulting output is malformed. This is an instance of CWE‑116—improper encoding or escaping of data, leading to invalid output. The malformed JSON can cause downstream log‑processing or indexing systems to reject or fail to ingest the affected log entries, effectively corrupting audit trails.

Affected Systems

Affected are Apache Log4j JSON Template Layout versions up through 2.25.3. The advisory recommends updating to 2.25.4 or newer to address the serialization flaw. Older releases—including the 3.0.0 alpha and beta lines—also use the same layout code and are impacted.

Risk and Exploitability

The CVSS score of 6.3 classifies this as a medium‑severity issue, and an EPSS of less than 1 % combined with its absence from the CISA KEV catalog indicates a low likelihood of active exploitation. An attacker must satisfy two conditions: the application must use JsonTemplateLayout and the attacker must be able to force the application to log a MapMessage or an object containing an attacker‑controlled non‑finite floating‑point value. When these prerequisites are met, the corrupt JSON may lead to downstream log‑processing failures, thereby impacting integrity and availability of audit trails.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Log4j JSON Template Layout to version 2.25.4 or newer; for full coverage move to 2.25.5 or 2.26.1.
  • Change the logging configuration to reference the updated layout and remove any legacy references to older layout templates.
  • Sanitize or replace any NaN, Infinity, or –Infinity values in logged MapMessage or object payloads before the logging call.

Generated by OpenCVE AI on July 31, 2026 at 17:56 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-w35j-pv5h-q9q9 Apache Log4j JSON Template Layout: Improper serialization of non-finite floating-point values in JsonTemplateLayout
History
Type Values Removed Values Added
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 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.
Type Values Removed Values Added
CPEs cpe:2.3:a:apache:log4j:*:*:*:*:*:*:*:*
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:*:*:*:*:*:*
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}

Type Values Removed Values Added
Weaknesses CWE-241
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Apache log4j
Vendors & Products Apache log4j
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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 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.
Title Apache Log4j JSON Template Layout: Improper serialization of non-finite floating-point values in JsonTemplateLayout
First Time appeared Apache
Apache log4j Layout Template Json
Weaknesses CWE-116
CPEs cpe:2.3:a:apache:log4j_layout_template_json:*:*:*:*:*:*:*:*
Vendors & Products Apache
Apache log4j Layout Template Json
References
Metrics cvssV4_0

{'score': 6.3, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N'}

Weaknesses
  • CWE-116

    Improper Encoding or Escaping of Output

  • CWE-241

    Improper Handling of Unexpected Data Type

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Jul 11, 2026, 4:55 AM
Reserved
Mar 28, 2026, 7:23 PM
Status
Modified
Published
Apr 10, 2026, 4:16 PM
Modified
Oct 26, 2026, 10:10 PM
Severity
Moderate
Public date
Apr 10, 2026, 3:43 PM