maven package report

Is org.apache.logging.log4j:log4j-layout-template-json safe?

1 known vulnerability, worst severity MODERATE.

cvss
6.3

how bad it is if exploited, out of 10

epss
0.70%

chance of exploitation in the next 30 days

xyz score
not scored

CyberXYZ composite, out of 10

fig. 01 — GHSA-w35j-pv5h-q9q9, the advisory selected below

// advisories

GHSA-w35j-pv5h-q9q9

MODERATECVE-2026-34481

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.

Affected
>= 2.14.0, < 2.25.4
Fixed in
2.25.4
Weakness
CWE-116
Published
2026-04-10
Source
github

GHSANVDMITREreferencereferencereferencereferencereferencereference

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so maven packages are not covered.

Checked 2026-09-22 at 03:48 UTC. The most recent advisory here was published 2026-04-10. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is org.apache.logging.log4j:log4j-layout-template-json safe? maven package security report | CyberXYZ