cve.bz

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

6.9 mediumExploit referenceEPSS 0.5%Fix available

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

On this page
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. Two groups of users are affected: * Those using Log4j1XmlLayout directly in a Log4j Core 2 configuration file. * Those using the Log4j 1 configuration compatibility layer with org.apache.log4j.xml.XMLLayout specified as the layout class. Users are advised to upgrade to Apache Log4j 1-to-Log4j 2 bridge version 2.25.4, which corrects this issue. Note: The Apache Log4j 1-to-Log4j 2 bridge is deprecated and will not be present in Log4j 3. Users are encouraged to consult the Log4j 1 to Log4j 2 migration guide https://logging.apache.org/log4j/2.x/migrate-from-log4j1.html , and specifically the section on eliminating reliance on the bridge.

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
0.5% (unchanged from 0.5% a week ago; 0.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 46th 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-34479 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-34479?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-34479?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-34479 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-34479

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-34479](https://cve.bz/cve/badge/CVE-2026-34479.svg)](https://cve.bz/cve/CVE-2026-34479)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Log4j 1 to Log4j 2 bridgefrom 2.7 before 2.25.4
Apache Software Foundation Apache Log4j 1 to Log4j 2 bridgefrom 3.0.0-alpha1 through 3.0.0-beta2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-h383-gmxw-35v2Mavenorg.apache.logging.log4j:log4j-core>=2.7 <2.25.42.25.4
GHSA-h383-gmxw-35v2Mavenorg.apache.logging.log4j:log4j-core>=3.0.0-beta1 <=3.0.0-beta2no fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14apache-log4j2no fix listedDEBIAN-CVE-2026-34479
Ubuntu18.04:LTS, 20.04:LTS, 22.04:LTS and 5 moreapache-log4j2, apache-log4j1.2no fix listedUBUNTU-CVE-2026-34479
UbuntuPro:14.04:LTSapache-log4j1.2no fix listedUBUNTU-CVE-2026-34479
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 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
Red Hat Offline Knowledge Portal 1.2.13offline-knowledge-portal/rhokp-rhel9:1779996999Fixed 2026-05-28RHSA-2026:21773
Red Hat Data Grid 8log4j-1.2-apiFix deferred
Red Hat Enterprise Linux 8log4j:2/log4jFix deferred
Red Hat Enterprise Linux 9log4jOut of support scope
Red Hat Fuse 7log4j-1.2-apiFix deferred
Red Hat JBoss Enterprise Application Platform 7log4j-1.2-apiFix deferred
Red Hat JBoss Enterprise Application Platform 8log4j-1.2-apiFix deferred
Red Hat JBoss Enterprise Application Platform Expansion Packlog4j-1.2-apiFix deferred
Red Hat Offline Knowledge Portalredhat-user-workloads/rhokp-core-encryptedFix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-modelmesh-rhel8Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-modelmesh-rhel9Fix deferred
streams for Apache Kafka 3log4j-1.2-apiFix deferred

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-34479.

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