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

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.

Published: 2026-04-10 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-34481 is rated Moderate Risk (40.3/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.56%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-34481

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.06% 0.56% +0.50%
2 2026-05-22 0.16% 0.06% -0.10%
3 2026-04-16 — 0.16% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-34481

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.3 4.0 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: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 Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network.
Attack complexity (AC:H)
Exploitation depends on constrained or hard-to-reproduce conditions.
Attack requirements (AT:P)
Additional preconditions must be present for exploitation.
Privileges required (PR:N)
No privileges are required.
User interaction (UI:N)
No user interaction is required.
Vulnerable system confidentiality impact (VC:N)
No confidentiality impact on the vulnerable system.
Vulnerable system integrity impact (VI:N)
No integrity impact on the vulnerable system.
Vulnerable system availability impact (VA:N)
No availability impact on the vulnerable system.
Subsequent system confidentiality impact (SC:N)
No confidentiality impact on subsequent systems.
Subsequent system integrity impact (SI:L)
Limited integrity impact on subsequent systems.
Subsequent system availability impact (SA:N)
No availability impact on subsequent systems.
Exploit maturity (threat) (E:X)
Not defined: no reliable threat intelligence; scoring assumes the worst case (equivalent to Attacked).
Confidentiality requirement (CR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Integrity requirement (IR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Availability requirement (AR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Modified attack vector (MAV:X)
Not defined: scoring uses the Base Attack Vector (AV).
Modified attack complexity (MAC:X)
Not defined: scoring uses the Base Attack Complexity (AC).
Modified attack requirements (MAT:X)
Not defined: scoring uses the Base Attack Requirements (AT).
Modified privileges required (MPR:X)
Not defined: scoring uses the Base Privileges Required (PR).
Modified user interaction (MUI:X)
Not defined: scoring uses the Base User Interaction (UI).
Modified vulnerable system confidentiality impact (MVC:X)
Not defined: scoring uses the Base VC metric.
Modified vulnerable system integrity impact (MVI:X)
Not defined: scoring uses the Base VI metric.
Modified vulnerable system availability impact (MVA:X)
Not defined: scoring uses the Base VA metric.
Modified subsequent system confidentiality impact (MSC:X)
Not defined: scoring uses the Base SC metric.
Modified subsequent system integrity impact (MSI:X)
Not defined: scoring uses the Base SI metric.
Modified subsequent system availability impact (MSA:X)
Not defined: scoring uses the Base SA metric.
Safety (supplemental) (S:X)
Not evaluated.
Automatable (supplemental) (AU:X)
Not evaluated.
Recovery (supplemental) (R:X)
Not evaluated.
Value density (supplemental) (V:X)
Not evaluated.
Vulnerability response effort (supplemental) (RE:X)
Not evaluated.
Provider urgency (supplemental) (U:X)
Not evaluated.
 — — [email protected]
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2026-34481

GitHub Security Advisory for CVE-2026-34481

GHSA-w35j-pv5h-q9q9 · Severity: medium · Ecosystem: maven — Apache Log4j JSON Template Layout: Improper serialization of non-finite floating-point values in JsonTemplateLayout

OS Trackers for CVE-2026-34481

vendor priority summary link
debian unimportant CVE-2026-34481 unimportant priority: Debian including 2 source packages (apache-log4j1.2, apache-log4j2), 10 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5, resolved 5. https://security-tracker.debian.org/tracker/CVE-2026-34481
redhat medium — https://access.redhat.com/security/cve/CVE-2026-34481
suse medium CVE-2026-34481 severity moderate: SUSE including 15 source package names (log4j, log4j-2.20.0-150200.4.33.1, …), 23 product×package rows across 8 product lines (SUSE Linux Enterprise Module for Basesystem 15 SP7, SUSE Linux Enterprise Server 12 SP4-LTSS, … (8 product lines)): Fixed 9, First Fixed 8, Known Not Affected 6. https://www.suse.com/security/cve/CVE-2026-34481/
ubuntu medium CVE-2026-34481 medium priority: Ubuntu including 2 source packages (apache-log4j1.2, apache-log4j2), 15 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): needs-triage 14, not-affected 1. https://ubuntu.com/security/CVE-2026-34481

Affected software / configurations for CVE-2026-34481

Vendor Product Version Raw CPE
apache log4j >= 2.14.0, < 2.25.4 cpe:2.3:a:apache:log4j:*:*:*:*:*:*:*:*
apache log4j 3.0.0 cpe:2.3:a:apache:log4j:3.0.0:alpha1:*:*:*:*:*:*
apache log4j 3.0.0 cpe:2.3:a:apache:log4j:3.0.0:alpha1_rc1:*:*:*:*:*:*
apache log4j 3.0.0 cpe:2.3:a:apache:log4j:3.0.0:alpha1_rc2:*:*:*:*:*:*
apache log4j 3.0.0 cpe:2.3:a:apache:log4j:3.0.0:beta1:*:*:*:*:*:*
apache log4j 3.0.0 cpe:2.3:a:apache:log4j:3.0.0:beta2:*:*:*:*:*:*
apache log4j 3.0.0 cpe:2.3:a:apache:log4j:3.0.0:beta3:*:*:*:*:*:*

References for CVE-2026-34481

cvelogic Threat Intelligence