CVE-2026-34481Apache Software Foundation Apache Log4j JSON Template Layout Improper Encoding or Escaping of Output
NVD
Vulnerability Summary
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.
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.
CVSS v4.0 Base Metrics — Score 6.3 (MEDIUM)
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:NAttack VectorNetwork
Attack ComplexityHigh
Attack RequirementsPresent
Privileges RequiredNone
User InteractionNone
Confidentiality (Vulnerable System)None
Integrity (Vulnerable System)None
Availability (Vulnerable System)None
Confidentiality (Subsequent System)None
Integrity (Subsequent System)Low
Availability (Subsequent System)None
Affected & Patched Versions
- Apache Software Foundation Apache Log4j JSON Template Layout >= 2.14.0 and < 2.25.4
- Apache Software Foundation Apache Log4j JSON Template Layout >= 3.0.0-alpha1 and <= 3.0.0-beta3
- Apache Software Foundation Apache Log4j JSON Template Layout 2.25.4
- Apache Software Foundation Apache Log4j JSON Template Layout 3.0.0-beta3
What to do
Fix it during your normal patch cycle. No exploitation is confirmed yet.
- Check whether you run Apache Software Foundation Apache Log4j JSON Template Layout and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Apr 10, 2026Published
- Jul 11, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new Apache Software Foundation Apache Log4j JSON Template Layout CVEsYou are reading CVE-2026-34481. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsRelated Coverage
External References
- Patchhttps://github.com/apache/logging-log4j2/pull/4080
- Referencehttps://logging.apache.org/security.html#CVE-2026-34481
- Referencehttps://logging.apache.org/cyclonedx/vdr.xml
- Referencehttps://logging.apache.org/log4j/2.x/manual/json-template-layout.html
- Referencehttps://lists.apache.org/thread/n34zdv00gbkdbzt2rx9rf5mqz6lhopcv
Data last checked: Nov 19, 2026 09:34 UTC