cve.bz

CVE-2026-34480 apache log4j: Improper Encoding or Escaping of Output

6.9 mediumEPSS 1.1%Fix available

Medium (6.9) in apache log4j. EPSS 1.1% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.logging.log4j:log4j-core 2.25.4.

On this page
Apache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets producing invalid XML output whenever a log message or MDC value contains such characters. The impact depends on the StAX implementation in use: * JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. * Alternative StAX implementations (e.g., Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
1.1% (unchanged from 1.1% a week ago; 1.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 65th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-04-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-116 Improper Encoding or Escaping of Output
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-34480 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-34480?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-34480?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-34480 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-34480

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-34480](https://cve.bz/cve/badge/CVE-2026-34480.svg)](https://cve.bz/cve/CVE-2026-34480)

HTML:

<a href="https://cve.bz/cve/CVE-2026-34480"><img src="https://cve.bz/cve/badge/CVE-2026-34480.svg" alt="CVE-2026-34480"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Log4j Corefrom 2.0-alpha1 before 2.25.4
Apache Software Foundation Apache Log4j Corefrom 3.0.0-alpha1 through 3.0.0-beta3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-3pxv-7cmr-fjr4Mavenorg.apache.logging.log4j:log4j-core>=2.0-alpha1 <2.25.42.25.4
GHSA-3pxv-7cmr-fjr4Mavenorg.apache.logging.log4j:log4j-core>=3.0.0-alpha1 <=3.0.0-beta3no fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14apache-log4j2, apache-log4j1.2no fix listedDEBIAN-CVE-2026-34480
Ubuntu18.04:LTS, 20.04:LTS, 22.04:LTS and 5 moreapache-log4j2, apache-log4j1.2no fix listedUBUNTU-CVE-2026-34480
UbuntuPro:14.04:LTSapache-log4j1.2no fix listedUBUNTU-CVE-2026-34480
openSUSETumbleweedlog4j2.20.0-2.1openSUSE-SU-2026:10544-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This flaw in Apache Log4j Core's XmlLayout component can lead to a denial of service in logging operations when log messages contain characters forbidden by the XML 1.0 specification. Systems processing these logs may fail to read records or the logging process may cease event delivery, impacting monitoring and auditing capabilities in affected Red Hat products. Red Hat products in their default configurations will be able to automatically recover, but some log messages may be lost.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
HawtIO HawtIO 4.4.0log4j-coreFixed 2026-06-10RHSA-2026:25089
Red Hat AMQ Broker 7.13.6log4j-coreFixed 2026-09-10RHSA-2026:66545
Red Hat AMQ Broker 7.14.1log4j-coreFixed 2026-09-10RHSA-2026:66488
Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16log4j-coreFixed 2026-07-09RHSA-2026:37390
Red Hat Data Grid 8.6.1log4j-coreFixed 2026-06-02RHSA-2026:22619
Red Hat Data Grid 8.6.1log4j-core-testFixed 2026-06-02RHSA-2026:22619
Streams for Apache Kafka 2.9.4log4j-coreFixed 2026-07-02RHSA-2026:34608
Streams for Apache Kafka 3.2.1log4j-coreFixed 2026-08-12RHSA-2026:54435
Red Hat Offline Knowledge Portal 1.2.13offline-knowledge-portal/rhokp-rhel9:1779996999Fixed 2026-05-28RHSA-2026:21773
Red Hat OpenShift AI 2.25rhoai/odh-modelmesh-rhel9:1783443816Fixed 2026-07-21RHSA-2026:42644
Red Hat AI Inference Serverredhat-user-workloads/rhaiis-cuda-ubi9-3-2-2Not affected
Red Hat AI Inference Serverredhat-user-workloads/rhaiis-cuda-ubi9-3-3Will not fix
Red Hat build of Apicurio Registry 2log4j-coreWill not fix
Red Hat build of Apicurio Registry 3log4j-coreWill not fix
Red Hat build of OptaPlanner 8log4j-coreAffected
Red Hat Enterprise Linux 8log4j:2/log4jNot affected
Red Hat Enterprise Linux 8pki-core:10.6/resteasyNot affected
Red Hat Enterprise Linux 8pki-deps:10.6/resteasyNot affected
Red Hat Enterprise Linux 9log4jWill not fix
Red Hat Enterprise Linux 9resteasyNot affected
28 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-34480.

Attack patterns (CAPEC)

  • CAPEC-73 User-Controlled Filename Likelihood: High · Severity: High
  • CAPEC-81 Web Server Logs Tampering Likelihood: Medium · Severity: High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-104 Cross Zone Scripting Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON