CVSS 4.0
6.9 mediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:NMedium (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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:NCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:Norg.apache.logging.log4j:log4j-core (Maven): fixed in 2.25.4Explain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Apache Software Foundation Apache Log4j Core | from 2.0-alpha1 before 2.25.4 |
| Apache Software Foundation Apache Log4j Core | from 3.0.0-alpha1 through 3.0.0-beta3 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-3pxv-7cmr-fjr4 | Maven | org.apache.logging.log4j:log4j-core | >=2.0-alpha1 <2.25.4 | 2.25.4 |
| GHSA-3pxv-7cmr-fjr4 | Maven | org.apache.logging.log4j:log4j-core | >=3.0.0-alpha1 <=3.0.0-beta3 | no fix published |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | apache-log4j2, apache-log4j1.2 | no fix listed | DEBIAN-CVE-2026-34480 |
| Ubuntu | 18.04:LTS, 20.04:LTS, 22.04:LTS and 5 more | apache-log4j2, apache-log4j1.2 | no fix listed | UBUNTU-CVE-2026-34480 |
| Ubuntu | Pro:14.04:LTS | apache-log4j1.2 | no fix listed | UBUNTU-CVE-2026-34480 |
| openSUSE | Tumbleweed | log4j | 2.20.0-2.1 | openSUSE-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 rates this Moderate.
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.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| HawtIO HawtIO 4.4.0 | log4j-core | Fixed 2026-06-10 | RHSA-2026:25089 |
| Red Hat AMQ Broker 7.13.6 | log4j-core | Fixed 2026-09-10 | RHSA-2026:66545 |
| Red Hat AMQ Broker 7.14.1 | log4j-core | Fixed 2026-09-10 | RHSA-2026:66488 |
| Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16 | log4j-core | Fixed 2026-07-09 | RHSA-2026:37390 |
| Red Hat Data Grid 8.6.1 | log4j-core | Fixed 2026-06-02 | RHSA-2026:22619 |
| Red Hat Data Grid 8.6.1 | log4j-core-test | Fixed 2026-06-02 | RHSA-2026:22619 |
| Streams for Apache Kafka 2.9.4 | log4j-core | Fixed 2026-07-02 | RHSA-2026:34608 |
| Streams for Apache Kafka 3.2.1 | log4j-core | Fixed 2026-08-12 | RHSA-2026:54435 |
| Red Hat Offline Knowledge Portal 1.2.13 | offline-knowledge-portal/rhokp-rhel9:1779996999 | Fixed 2026-05-28 | RHSA-2026:21773 |
| Red Hat OpenShift AI 2.25 | rhoai/odh-modelmesh-rhel9:1783443816 | Fixed 2026-07-21 | RHSA-2026:42644 |
| Red Hat AI Inference Server | redhat-user-workloads/rhaiis-cuda-ubi9-3-2-2 | Not affected | |
| Red Hat AI Inference Server | redhat-user-workloads/rhaiis-cuda-ubi9-3-3 | Will not fix | |
| Red Hat build of Apicurio Registry 2 | log4j-core | Will not fix | |
| Red Hat build of Apicurio Registry 3 | log4j-core | Will not fix | |
| Red Hat build of OptaPlanner 8 | log4j-core | Affected | |
| Red Hat Enterprise Linux 8 | log4j:2/log4j | Not affected | |
| Red Hat Enterprise Linux 8 | pki-core:10.6/resteasy | Not affected | |
| Red Hat Enterprise Linux 8 | pki-deps:10.6/resteasy | Not affected | |
| Red Hat Enterprise Linux 9 | log4j | Will not fix | |
| Red Hat Enterprise Linux 9 | resteasy | Not 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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.