maven package report

Is org.apache.logging.log4j:log4j-1.2-api safe?

1 known vulnerability, worst severity MODERATE.

cvss
6.9

how bad it is if exploited, out of 10

epss
0.50%

chance of exploitation in the next 30 days

xyz score
not scored

CyberXYZ composite, out of 10

fig. 01 — GHSA-h383-gmxw-35v2, the advisory selected below

// advisories

GHSA-h383-gmxw-35v2

MODERATECVE-2026-34479

The Log4j1XmlLayout from the Apache Log4j 1-to-Log4j 2 bridge fails to escape characters forbidden by the XML 1.0 standard, producing malformed XML output. Conforming XML parsers are required to reject documents containing such characters with a fatal error, which may cause downstream log processing systems to drop or fail to index affected records.

Affected
>= 2.7, < 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:47 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-1.2-api safe? maven package security report | CyberXYZ