- Veröffentlicht
- 10.04.2026 17:43
- Zuletzt geändert
- 29.10.2026
- EPSS (30 Tage)
- 0.7 %
- 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.
Apache Log4j's JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records.
An attacker can exploit this issue only if both of the following conditions are met:
* The application uses JsonTemplateLayout.
* The application logs a MapMessage, or logs an object directly (e.g., via Logger.info(Object), which wraps it in an ObjectMessage), where the message contains an attacker-controlled floating-point value.
Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.
Note: The fix released in version 2.25.4 did not cover all affected code paths. CVE-2026-49844 was assigned to the remaining issue, which concerns the MapMessage.asJson() serialization in Apache Log4j API and is fixed in versions 2.25.5 and 2.26.1.
Status beim Hersteller
SUSE stuft seine Produktlinien ein: 22 betroffen, 13 behoben, 11 nicht betroffen.
Oracle Retail Applications 14.2
Betroffen
Oracle Retail Applications 15.0
Betroffen
Oracle Retail Applications 16.0
Betroffen
Oracle Spatial Studio 23.2.1
Betroffen
Oracle Spatial Studio 24.2
Betroffen
Red Hat Enterprise Linux 9
Betroffenwird nicht behoben
log4j, log4j-jcl, log4j-slf4j
Red Hat JBoss Enterprise Application Platform 7
Betroffenwird nicht behoben
log4j-layout-template-json
Red Hat Offline Knowledge Portal
BetroffenFix ausstehend
redhat-user-workloads/rhocc-mimir-tenant/mimir/rhokp-core-encrypted
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
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 (11)
Red Hat Enterprise Linux 8Nicht betroffenverwundbarer Code nicht enthaltenlog4j, log4j-jcl, log4j-slf4j, log4j-web
Red Hat JBoss Enterprise Application Platform 8Nicht betroffenverwundbarer Code nicht enthaltenlog4j-layout-template-json
Red Hat JBoss Enterprise Application Platform Expansion PackNicht betroffenverwundbarer Code nicht enthaltenlog4j-layout-template-json
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:9log4jkein Fix bekanntCVE-2026-34481
Red Hat:enterprise_linux:9log4j-jclkein Fix bekanntCVE-2026-34481
Red Hat:enterprise_linux:9log4j-slf4jkein Fix bekanntCVE-2026-34481
Weitere betroffene Pakete (58)
CVEApache Software Foundation/Apache Log4j JSON Template Layout2.14.0 → 2.25.4CVE-2026-34481
Debian:12apache-log4j2kein Fix bekanntDEBIAN-CVE-2026-34481
Debian:13apache-log4j2kein Fix bekanntDEBIAN-CVE-2026-34481
Debian:14apache-log4j2kein Fix bekanntDEBIAN-CVE-2026-34481
Mavenorg.apache.logging.log4j:log4j-layout-template-json2.14.0 → 2.25.4GHSA-w35j-pv5h-q9q9
Mavenorg.apache.logging.log4j:log4j-layout-template-jsonkein Fix bekanntGHSA-w35j-pv5h-q9q9
NVDapache:log4j2.14.0 → 2.25.4CVE-2026-34481
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.1-tuxcare.1CLSA-2026-1790709023
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.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-api2.23.1-tuxcare.1CLSA-2026-1787471222
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.22.1-tuxcare.1CLSA-2026-1780447835
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.24.3-tuxcare.1CLSA-2026-1784683011
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.18.0-tuxcare.1CLSA-2026-1784769542
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.17.2-tuxcare.2CLSA-2026-1785727932
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.23.1-tuxcare.1CLSA-2026-1787471222
TuxCare:Mavenorg.apache.logging.log4j:log4j-core2.24.1-tuxcare.1CLSA-2026-1790709023
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.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.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.24.3-tuxcare.1CLSA-2026-1784683011
TuxCare:Mavenorg.apache.logging.log4j:log4j-layout-template-json2.18.0-tuxcare.1CLSA-2026-1784769542
TuxCare:Mavenorg.apache.logging.log4j:log4j-layout-template-json2.17.1-tuxcare.3CLSA-2026-1784769579
TuxCare:Mavenorg.apache.logging.log4j:log4j-layout-template-json2.17.2-tuxcare.2CLSA-2026-1785727932
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-34481
Ubuntu:18.04:LTSapache-log4j2kein Fix bekanntUBUNTU-CVE-2026-34481
Ubuntu:20.04:LTSapache-log4j1.2kein Fix bekanntUBUNTU-CVE-2026-34481
Ubuntu:20.04:LTSapache-log4j2kein Fix bekanntUBUNTU-CVE-2026-34481
Ubuntu:22.04:LTSapache-log4j1.2kein Fix bekanntUBUNTU-CVE-2026-34481
Ubuntu:22.04:LTSapache-log4j2kein Fix bekanntUBUNTU-CVE-2026-34481
Ubuntu:24.04:LTSapache-log4j1.2kein Fix bekanntUBUNTU-CVE-2026-34481
Ubuntu:24.04:LTSapache-log4j2kein Fix bekanntUBUNTU-CVE-2026-34481
Ubuntu:25.10apache-log4j1.2kein Fix bekanntUBUNTU-CVE-2026-34481
Ubuntu:25.10apache-log4j2kein Fix bekanntUBUNTU-CVE-2026-34481
Ubuntu:26.04:LTSapache-log4j1.2kein Fix bekanntUBUNTU-CVE-2026-34481
Ubuntu:26.04:LTSapache-log4j2kein Fix bekanntUBUNTU-CVE-2026-34481
Ubuntu:26.10apache-log4j1.2kein Fix bekanntUBUNTU-CVE-2026-34481
Ubuntu:26.10apache-log4j2kein Fix bekanntUBUNTU-CVE-2026-34481
Ubuntu:Pro:14.04:LTSapache-log4j1.2kein Fix bekanntUBUNTU-CVE-2026-34481
Ubuntu:Pro:16.04:LTSapache-log4j1.2kein Fix bekanntUBUNTU-CVE-2026-34481
Ubuntu:Pro:16.04:LTSapache-log4j2kein Fix bekanntUBUNTU-CVE-2026-34481
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/4080
- logging.apache.org/security.html
- logging.apache.org/cyclonedx/vdr.xml
- logging.apache.org/log4j/2.x/manual/json-template-layout.html
- lists.apache.org/thread/n34zdv00gbkdbzt2rx9rf5mqz6lhopcv
- wid.cert-bund.de/.well-known/csaf/white/2026/wid-sec-w-2026-2432.json
- wid.cert-bund.de/portal/wid/securityadvisory
- www.oracle.com/security-alerts/cpujul2026.html
- wid.cert-bund.de/.well-known/csaf/white/2026/wid-sec-w-2026-2901.json
- wid.cert-bund.de/portal/wid/securityadvisory
- www.oracle.com/security-alerts/cspuaug2026.html
- www.suse.com/security/cve/CVE-2026-34481
- www.suse.com/support/security/rating/
- bugzilla.suse.com/1262093
- lists.suse.com/pipermail/sle-updates/2026-May/046426.html
- security-tracker.debian.org/tracker/CVE-2026-34481
- nvd.nist.gov/vuln/detail/CVE-2026-34481
- github.com/apache/logging-log4j2
- www.openwall.com/lists/oss-security/2026/04/10/10
- ubuntu.com/security/CVE-2026-34481
- www.cve.org/CVERecord
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-34481.json
- access.redhat.com/security/cve/CVE-2026-34481
- bugzilla.redhat.com/show_bug.cgi