- Veröffentlicht
- 10.04.2026 17:41
- Zuletzt geändert
- 17.11.2026
- EPSS (30 Tage)
- 0.5 %
- CVSS-Vektor
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Beschreibung
Originaltext der Quelle, nicht übersetzt.
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.
Status beim Hersteller
SUSE stuft seine Produktlinien ein: 24 betroffen, 8 behoben, 8 nicht betroffen.
Red Hat Data Grid 8
BetroffenFix zurückgestellt
log4j-1.2-api
Red Hat Enterprise Linux 8
BetroffenFix zurückgestellt
log4j, log4j-jcl, log4j-slf4j, log4j-web
Red Hat Enterprise Linux 9
Betroffenaußerhalb des Supports
log4j, log4j-jcl, log4j-slf4j
Red Hat Fuse 7
BetroffenFix zurückgestellt
log4j-1.2-api
Red Hat JBoss Enterprise Application Platform 7
BetroffenFix zurückgestellt
log4j-1.2-api
Red Hat JBoss Enterprise Application Platform 8
BetroffenFix zurückgestellt
log4j-1.2-api
Red Hat JBoss Enterprise Application Platform Expansion Pack
BetroffenFix zurückgestellt
log4j-1.2-api
Red Hat Offline Knowledge Portal
BetroffenFix zurückgestellt
redhat-user-workloads/rhocc-mimir-tenant/mimir/rhokp-core-encrypted
Red Hat OpenShift AI (RHOAI)
BetroffenFix zurückgestellt
rhoai/odh-modelmesh-rhel8, rhoai/odh-modelmesh-rhel9
SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
Betroffen
log4j, log4j-javadoc, log4j-jcl, log4j-slf4j
SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
Betroffen
log4j, log4j-javadoc, log4j-jcl, log4j-slf4j
SUSE Linux Enterprise Server 15 SP3
Betroffen
log4j, log4j-javadoc, log4j-jcl, log4j-slf4j
SUSE Linux Enterprise Server 15 SP3-LTSS
Betroffen
log4j, log4j-javadoc, log4j-jcl, log4j-slf4j
SUSE Linux Enterprise Server 15 SP4
Betroffen
log4j, log4j-javadoc, log4j-jcl, log4j-slf4j
SUSE Linux Enterprise Server 15 SP4-LTSS
Betroffen
log4j, log4j-javadoc, log4j-jcl, log4j-slf4j
SUSE Linux Enterprise Server 15 SP5
Betroffen
log4j, log4j-javadoc, log4j-jcl, log4j-slf4j
SUSE Linux Enterprise Server 15 SP5-LTSS
Betroffen
log4j, log4j-javadoc, log4j-jcl, log4j-slf4j
SUSE Linux Enterprise Server 15 SP6
Betroffen
log4j, log4j-javadoc, log4j-jcl, log4j-slf4j
SUSE Linux Enterprise Server 15 SP6-LTSS
Betroffen
log4j, log4j-javadoc, log4j-jcl, log4j-slf4j
SUSE Linux Enterprise Server for SAP Applications 15 SP4
Betroffen
log4j, log4j-javadoc, log4j-jcl, log4j-slf4j
SUSE Linux Enterprise Server for SAP Applications 15 SP5
Betroffen
log4j, log4j-javadoc, log4j-jcl, log4j-slf4j
SUSE Linux Enterprise Server for SAP Applications 15 SP6
Betroffen
log4j, log4j-javadoc, log4j-jcl, log4j-slf4j
openSUSE Leap 15.6
Betroffen
log4j, log4j-javadoc, log4j-jcl, log4j-slf4j
streams for Apache Kafka 3
BetroffenFix zurückgestellt
log4j-1.2-api
Red Hat Offline Knowledge Portal 1.2.13
Behoben
offline-knowledge-portal/rhokp-rhel9
RHSA-2026:21773
SUSE Linux Enterprise Desktop 15 SP7
Behoben
log4j-2.20.0-150200.4.33.1, log4j-javadoc-2.20.0-150200.4.33.1, log4j-jcl-2.20.0-150200.4.33.1, log4j-slf4j-2.20.0-150200.4.33.1
SUSE Linux Enterprise High Performance Computing 15 SP7
Behoben
log4j-2.20.0-150200.4.33.1, log4j-javadoc-2.20.0-150200.4.33.1, log4j-jcl-2.20.0-150200.4.33.1, log4j-slf4j-2.20.0-150200.4.33.1
SUSE Linux Enterprise Module for Basesystem 15 SP7
Behoben
log4j-2.20.0-150200.4.33.1, log4j-javadoc-2.20.0-150200.4.33.1, log4j-jcl-2.20.0-150200.4.33.1, log4j-slf4j-2.20.0-150200.4.33.1
SUSE Linux Enterprise Server 15 SP4-TERADATA
Behoben
log4j-2.20.0-150200.4.33.1, log4j-javadoc-2.20.0-150200.4.33.1, log4j-jcl-2.20.0-150200.4.33.1, log4j-slf4j-2.20.0-150200.4.33.1
SUSE Linux Enterprise Server 15 SP7
Behoben
log4j-2.20.0-150200.4.33.1, log4j-javadoc-2.20.0-150200.4.33.1, log4j-jcl-2.20.0-150200.4.33.1, log4j-slf4j-2.20.0-150200.4.33.1
SUSE Linux Enterprise Server for SAP Applications 15 SP7
Behoben
log4j-2.20.0-150200.4.33.1, log4j-javadoc-2.20.0-150200.4.33.1, log4j-jcl-2.20.0-150200.4.33.1, log4j-slf4j-2.20.0-150200.4.33.1
openSUSE Tumbleweed
Behoben
log4j-2.20.0-2.1, log4j-bom-2.20.0-2.1, log4j-javadoc-2.20.0-2.1, log4j-jcl-2.20.0-2.1, log4j-jmx-gui-2.20.0-2.1, log4j-nosql-2.20.0-2.1, log4j-slf4j-2.20.0-2.1, log4j-taglib-2.20.0-2.1, log4j-web-2.20.0-2.1
Nicht betroffen (8)
SUSE Linux Enterprise Server 12 SP4Nicht betroffenlog4j
SUSE Linux Enterprise Server 12 SP4-LTSSNicht betroffenlog4j
SUSE Linux Enterprise Server 12 SP5Nicht betroffenlog4j
SUSE Linux Enterprise Server 12 SP5-LTSSNicht betroffenlog4j
SUSE Linux Enterprise Server 12 SP5-LTSS Extended SecurityNicht betroffenlog4j
SUSE Linux Enterprise Server 15 SP1Nicht betroffenlog4j, log4j-manual
SUSE Linux Enterprise Server 15 SP1-LTSSNicht betroffenlog4j, log4j-manual
SUSE Linux Enterprise Server Teradata 12 SP3Nicht betroffenlog4j
Betroffene Pakete im beobachteten Stack
Red Hat:enterprise_linux:8log4jkein Fix bekanntCVE-2026-34479
Red Hat:enterprise_linux:8log4j-jclkein Fix bekanntCVE-2026-34479
Red Hat:enterprise_linux:8log4j-slf4jkein Fix bekanntCVE-2026-34479
Red Hat:enterprise_linux:8log4j-webkein Fix bekanntCVE-2026-34479
Red Hat:enterprise_linux:9log4jkein Fix bekanntCVE-2026-34479
Red Hat:enterprise_linux:9log4j-jclkein Fix bekanntCVE-2026-34479
Red Hat:enterprise_linux:9log4j-slf4jkein Fix bekanntCVE-2026-34479
Weitere betroffene Pakete (84)
CVEApache Software Foundation/Apache Log4j 1 to Log4j 2 bridge2.7 → 2.25.4CVE-2026-34479
Debian:12apache-log4j2kein Fix bekanntDEBIAN-CVE-2026-34479
Debian:13apache-log4j2kein Fix bekanntDEBIAN-CVE-2026-34479
Debian:14apache-log4j2kein Fix bekanntDEBIAN-CVE-2026-34479
Docker Hardened Images:Alpine:3.24janusgraph-1.0kein Fix bekanntDHI-ay4s-f4pm-dxzq-hcit
Docker Hardened Images:Alpine:3.24janusgraph-1.1kein Fix bekanntDHI-ay4s-f4pm-dxzq-hcit
Docker Hardened Images:Debian:13janusgraph-1.0kein Fix bekanntDHI-ay4s-f4pm-dxzq-hcit
Docker Hardened Images:Debian:13janusgraph-1.1kein Fix bekanntDHI-ay4s-f4pm-dxzq-hcit
Mavenorg.apache.logging.log4j:log4j-corekein Fix bekanntGHSA-h383-gmxw-35v2
Mavenorg.apache.logging.log4j:log4j-core2.7 → 2.25.4GHSA-h383-gmxw-35v2
NVDapache:log4j2.7 → 2.25.4CVE-2026-34479
TuxCare:AlmaLinux:9.2log4j2.17.2-1.el9_2.tuxcare.els1CLSA-2026-1780054786
TuxCare:AlmaLinux:9.2log4j-jcl2.17.2-1.el9_2.tuxcare.els1CLSA-2026-1780054786
TuxCare:AlmaLinux:9.2log4j-slf4j2.17.2-1.el9_2.tuxcare.els1CLSA-2026-1780054786
TuxCare:AlmaLinux:9.2log4j-web2.17.2-1.el9_2.tuxcare.els1CLSA-2026-1780054786
TuxCare:AlmaLinux:9.6log4j2.17.2-1.el9.tuxcare.els1CLSA-2026-1779124827
TuxCare:AlmaLinux:9.6log4j-jcl2.17.2-1.el9.tuxcare.els1CLSA-2026-1779124827
TuxCare:AlmaLinux:9.6log4j-slf4j2.17.2-1.el9.tuxcare.els1CLSA-2026-1779124827
TuxCare:AlmaLinux:9.6log4j-web2.17.2-1.el9.tuxcare.els1CLSA-2026-1779124827
TuxCare:Mavenorg.apache.logging.log4j:log4j-1.2-api2.17.2-tuxcare.1CLSA-2026-1776991059
TuxCare:Mavenorg.apache.logging.log4j:log4j-1.2-api2.22.1-tuxcare.1CLSA-2026-1780447835
TuxCare:Mavenorg.apache.logging.log4j:log4j-1.2-api2.23.1-tuxcare.1CLSA-2026-1787471222
TuxCare:Mavenorg.apache.logging.log4j:log4j-1.2-api2.24.3-tuxcare.2CLSA-2026-1787726168
TuxCare:Mavenorg.apache.logging.log4j:log4j-1.2-api2.17.1-tuxcare.4CLSA-2026-1788442788
TuxCare:Mavenorg.apache.logging.log4j:log4j-1.2-api2.24.1-tuxcare.1CLSA-2026-1790709023
TuxCare:Mavenorg.apache.logging.log4j:log4j-1.2-api2.13.3-tuxcare.1CLSA-2026-1790872639
TuxCare:Mavenorg.apache.logging.log4j:log4j-1.2-api2.11.1-tuxcare.1CLSA-2026-1790941398
TuxCare:Mavenorg.apache.logging.log4j:log4j-1.2-api2.19.0-tuxcare.1CLSA-2026-1790944047
TuxCare:Mavenorg.apache.logging.log4j:log4j-1.2-api2.20.0-tuxcare.2CLSA-2026-1792696729
TuxCare:Mavenorg.apache.logging.log4j:log4j-1.2-api2.12.4-tuxcare.2CLSA-2026-1792756951
TuxCare:Mavenorg.apache.logging.log4j:log4j-1.2-api2.21.1-tuxcare.1CLSA-2026-1793052872
TuxCare:Mavenorg.apache.logging.log4j:log4j-1.2-api2.25.2-tuxcare.1CLSA-2026-1793354113
TuxCare:Mavenorg.apache.logging.log4j:log4j-1.2-api2.8.2-tuxcare.2CLSA-2026-1793723595
TuxCare:Mavenorg.apache.logging.log4j:log4j-1.2-api2.9.1-tuxcare.2CLSA-2026-1793724321
TuxCare:Mavenorg.apache.logging.log4j:log4j-1.2-api2.7-tuxcare.2CLSA-2026-1793724931
TuxCare:Mavenorg.apache.logging.log4j:log4j-1.2-api2.10.0-tuxcare.2CLSA-2026-1793725664
TuxCare:Mavenorg.apache.logging.log4j:log4j-api2.23.1-tuxcare.1CLSA-2026-1787471222
TuxCare:Mavenorg.apache.logging.log4j:log4j-api2.24.3-tuxcare.2CLSA-2026-1787726168
TuxCare:Mavenorg.apache.logging.log4j:log4j-api2.20.0-tuxcare.2CLSA-2026-1792696729
TuxCare:Mavenorg.apache.logging.log4j:log4j-api2.21.1-tuxcare.1CLSA-2026-1793052872
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.17.2-tuxcare.1CLSA-2026-1776991059
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.22.1-tuxcare.1CLSA-2026-1780447835
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.23.1-tuxcare.1CLSA-2026-1787471222
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.24.3-tuxcare.2CLSA-2026-1787726168
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.17.1-tuxcare.4CLSA-2026-1788442788
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.24.1-tuxcare.1CLSA-2026-1790709023
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.13.3-tuxcare.1CLSA-2026-1790872639
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.11.1-tuxcare.1CLSA-2026-1790941398
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.19.0-tuxcare.1CLSA-2026-1790944047
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.20.0-tuxcare.2CLSA-2026-1792696729
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.12.4-tuxcare.2CLSA-2026-1792756951
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.21.1-tuxcare.1CLSA-2026-1793052872
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.25.2-tuxcare.1CLSA-2026-1793354113
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.8.2-tuxcare.2CLSA-2026-1793723595
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.9.1-tuxcare.2CLSA-2026-1793724321
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.7-tuxcare.2CLSA-2026-1793724931
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.10.0-tuxcare.2CLSA-2026-1793725664
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.17.0-tuxcare.2CLSA-2026-1793882002
TuxCare:Mavenorg.apache.logging.log4j:log4j-layout-template-json2.22.1-tuxcare.1CLSA-2026-1780447835
TuxCare:Mavenorg.apache.logging.log4j:log4j-layout-template-json2.23.1-tuxcare.1CLSA-2026-1787471222
TuxCare:Mavenorg.apache.logging.log4j:log4j-layout-template-json2.24.1-tuxcare.1CLSA-2026-1790709023
TuxCare:Mavenorg.apache.logging.log4j:log4j-layout-template-json2.19.0-tuxcare.1CLSA-2026-1790944047
TuxCare:Mavenorg.apache.logging.log4j:log4j-layout-template-json2.20.0-tuxcare.2CLSA-2026-1792696729
TuxCare:Mavenorg.apache.logging.log4j:log4j-layout-template-json2.21.1-tuxcare.1CLSA-2026-1793052872
TuxCare:Mavenorg.apache.logging.log4j:log4j-layout-template-json2.25.2-tuxcare.1CLSA-2026-1793354113
TuxCare:Mavenorg.apache.logging.log4j:log4j-layout-template-json2.17.0-tuxcare.2CLSA-2026-1793882002
Ubuntu:18.04:LTSapache-log4j1.2kein Fix bekanntUBUNTU-CVE-2026-34479
Ubuntu:18.04:LTSapache-log4j2kein Fix bekanntUBUNTU-CVE-2026-34479
Ubuntu:20.04:LTSapache-log4j1.2kein Fix bekanntUBUNTU-CVE-2026-34479
Ubuntu:20.04:LTSapache-log4j2kein Fix bekanntUBUNTU-CVE-2026-34479
Ubuntu:22.04:LTSapache-log4j1.2kein Fix bekanntUBUNTU-CVE-2026-34479
Ubuntu:22.04:LTSapache-log4j2kein Fix bekanntUBUNTU-CVE-2026-34479
Ubuntu:24.04:LTSapache-log4j1.2kein Fix bekanntUBUNTU-CVE-2026-34479
Ubuntu:24.04:LTSapache-log4j2kein Fix bekanntUBUNTU-CVE-2026-34479
Ubuntu:25.10apache-log4j1.2kein Fix bekanntUBUNTU-CVE-2026-34479
Ubuntu:25.10apache-log4j2kein Fix bekanntUBUNTU-CVE-2026-34479
Ubuntu:26.04:LTSapache-log4j1.2kein Fix bekanntUBUNTU-CVE-2026-34479
Ubuntu:26.04:LTSapache-log4j2kein Fix bekanntUBUNTU-CVE-2026-34479
Ubuntu:26.10apache-log4j1.2kein Fix bekanntUBUNTU-CVE-2026-34479
Ubuntu:26.10apache-log4j2kein Fix bekanntUBUNTU-CVE-2026-34479
Ubuntu:Pro:14.04:LTSapache-log4j1.2kein Fix bekanntUBUNTU-CVE-2026-34479
Ubuntu:Pro:16.04:LTSapache-log4j1.2kein Fix bekanntUBUNTU-CVE-2026-34479
Ubuntu:Pro:16.04:LTSapache-log4j2kein Fix bekanntUBUNTU-CVE-2026-34479
openSUSE:Tumbleweedlog4j2.20.0-2.1openSUSE-SU-2026:10544-1
Empfohlene Prüfung
- Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
- Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
- Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · ohne Login) ist aus dem CVSS-Vektor abgeleitet.
Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.
Referenzen
- github.com/apache/logging-log4j2/pull/4078
- logging.apache.org/security.html
- logging.apache.org/cyclonedx/vdr.xml
- logging.apache.org/log4j/2.x/migrate-from-log4j1.html
- lists.apache.org/thread/gd0hp6mj17rn3kj279vgy4p7kd4zz5on
- www.suse.com/security/cve/CVE-2026-34479
- www.suse.com/support/security/rating/
- bugzilla.suse.com/1262091
- lists.suse.com/pipermail/sle-updates/2026-May/046426.html
- errata.tuxcare.com/els_os/tuxcare9.6esu/CLSA-2026-1779124827.html
- errata.tuxcare.com/els_os/almalinux9.2esu/CLSA-2026-1780054786.html
- security-tracker.debian.org/tracker/CVE-2026-34479
- scout.docker.com/v/DHI-ay4s-f4pm-dxzq-hcit
- nvd.nist.gov/vuln/detail/CVE-2026-34479
- www.openwall.com/lists/oss-security/2026/04/10/8
- github.com/advisories/GHSA-h383-gmxw-35v2
- ubuntu.com/security/CVE-2026-34479
- people.ubuntu.com/~ubuntu-security/cve/CVE-2026-34479
- github.com/apache/logging-log4j2
- www.cve.org/CVERecord
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-34479.json
- access.redhat.com/security/cve/CVE-2026-34479
- bugzilla.redhat.com/show_bug.cgi