{"id":"CVE-2026-34481","aliases":["CLSA-2026-1780447835","CLSA-2026-1784683011","CLSA-2026-1784769542","CLSA-2026-1784769579","CLSA-2026-1785727932","CLSA-2026-1787471222","CLSA-2026-1790709023","CLSA-2026-1790944047","CLSA-2026-1792696729","CLSA-2026-1793052872","CLSA-2026-1793354113","CLSA-2026-1793882002","DEBIAN-CVE-2026-34481","EUVD-2026-21412","GHSA-w35j-pv5h-q9q9","OESA-2026-3153","ROOT-APP-MAVEN-CVE-2026-34481","SUSE-SU-2026:1843-1","UBUNTU-CVE-2026-34481","openSUSE-SU-2026:10544-1"],"status":"published","title":"Apache Log4j JSON Template Layout: Improper serialization of non-finite floating-point values in JsonTemplateLayout","description":"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.\n\nAn attacker can exploit this issue only if both of the following conditions are met:\n\n  *  The application uses JsonTemplateLayout.\n  *  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.\n\n\nUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.\n\nNote: 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.","severity":{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.00718,"percentile":0.54333,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-116"],"published":"2026-04-10T15:43:00Z","modified":"2026-11-06T13:15:03Z","fixes":[{"ecosystem":"Maven","package":"org.apache.logging.log4j:log4j-layout-template-json","fixed_in":["2.25.4"],"sources":["ghsa","osv"]},{"ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-layout-template-json","fixed_in":["2.17.1-tuxcare.3"],"sources":["osv"]},{"ecosystem":"Root:Maven","package":"org.apache.logging.log4j:log4j-layout-template-json","fixed_in":["2.23.1-aikido.2","2.21.1-aikido.5","2.23.1-aikido.3","2.24.3-aikido.1"],"sources":["osv"]},{"ecosystem":"Root:Maven","package":"io.root.org.apache.logging.log4j:log4j-layout-template-json","fixed_in":["2.23.1-root.io.1","2.21.1-root.io.1","2.23.1-root.io.2","2.21.1-root.io.4","2.21.1-root.io.5","2.23.1-root.io.3","2.24.3-root.io.1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"Maven","package":"org.apache.logging.log4j:log4j-layout-template-json","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.14.0"},{"fixed":"2.25.4"}]}]},{"source":"ghsa","ecosystem":"Maven","package":"org.apache.logging.log4j:log4j-layout-template-json","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0-alpha1"},{"last_affected":"3.0.0-beta3"}]}]},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-1.2-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.22.1"},{"fixed":"2.22.1-tuxcare.1"}]}],"versions":["2.22.1"],"bundled":3},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.22.1"},{"fixed":"2.22.1-tuxcare.1"}]}],"versions":["2.22.1"],"bundled":3},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-layout-template-json","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.22.1"},{"fixed":"2.22.1-tuxcare.1"}]}],"versions":["2.22.1"],"bundled":3},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.24.3"},{"fixed":"2.24.3-tuxcare.1"}]}],"versions":["2.24.3"],"bundled":2},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-layout-template-json","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.24.3"},{"fixed":"2.24.3-tuxcare.1"}]}],"versions":["2.24.3"],"bundled":2},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.18.0"},{"fixed":"2.18.0-tuxcare.1"}]}],"versions":["2.18.0"],"bundled":2},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-layout-template-json","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.18.0"},{"fixed":"2.18.0-tuxcare.1"}]}],"versions":["2.18.0"],"bundled":2},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-layout-template-json","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.17.1"},{"fixed":"2.17.1-tuxcare.3"}]}],"versions":["2.17.1","2.17.1-tuxcare.1","2.17.1-tuxcare.2"]},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.17.2"},{"fixed":"2.17.2-tuxcare.2"}]}],"versions":["2.17.2","2.17.2-tuxcare.1"],"bundled":3},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-layout-template-json","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.17.2"},{"fixed":"2.17.2-tuxcare.2"}]}],"versions":["2.17.2","2.17.2-tuxcare.1"],"bundled":3},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-1.2-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.23.1"},{"fixed":"2.23.1-tuxcare.1"}]}],"versions":["2.23.1"],"bundled":3},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.23.1"},{"fixed":"2.23.1-tuxcare.1"}]}],"versions":["2.23.1"],"bundled":3},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.23.1"},{"fixed":"2.23.1-tuxcare.1"}]}],"versions":["2.23.1"],"bundled":3},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-layout-template-json","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.23.1"},{"fixed":"2.23.1-tuxcare.1"}]}],"versions":["2.23.1"],"bundled":3},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-1.2-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.24.1"},{"fixed":"2.24.1-tuxcare.1"}]}],"versions":["2.24.1"],"bundled":3},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.24.1"},{"fixed":"2.24.1-tuxcare.1"}]}],"versions":["2.24.1"],"bundled":3},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-layout-template-json","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.24.1"},{"fixed":"2.24.1-tuxcare.1"}]}],"versions":["2.24.1"],"bundled":3},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-1.2-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.19.0"},{"fixed":"2.19.0-tuxcare.1"}]}],"versions":["2.19.0"],"bundled":3},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.19.0"},{"fixed":"2.19.0-tuxcare.1"}]}],"versions":["2.19.0"],"bundled":3},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-layout-template-json","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.19.0"},{"fixed":"2.19.0-tuxcare.1"}]}],"versions":["2.19.0"],"bundled":3},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-1.2-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.20.0"},{"fixed":"2.20.0-tuxcare.2"}]}],"versions":["2.20.0","2.20.0-tuxcare.1"],"bundled":5},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.20.0"},{"fixed":"2.20.0-tuxcare.2"}]}],"versions":["2.20.0","2.20.0-tuxcare.1"],"bundled":5},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.20.0"},{"fixed":"2.20.0-tuxcare.2"}]}],"versions":["2.20.0","2.20.0-tuxcare.1"],"bundled":5},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-layout-template-json","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.20.0"},{"fixed":"2.20.0-tuxcare.2"}]}],"versions":["2.20.0","2.20.0-tuxcare.1"],"bundled":5},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-1.2-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.21.1"},{"fixed":"2.21.1-tuxcare.1"}]}],"versions":["2.21.1"],"bundled":4},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.21.1"},{"fixed":"2.21.1-tuxcare.1"}]}],"versions":["2.21.1"],"bundled":4},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.21.1"},{"fixed":"2.21.1-tuxcare.1"}]}],"versions":["2.21.1"],"bundled":4},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-layout-template-json","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.21.1"},{"fixed":"2.21.1-tuxcare.1"}]}],"versions":["2.21.1"],"bundled":4},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-1.2-api","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.25.2"},{"fixed":"2.25.2-tuxcare.1"}]}],"versions":["2.25.2"],"bundled":5},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.25.2"},{"fixed":"2.25.2-tuxcare.1"}]}],"versions":["2.25.2"],"bundled":5},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-layout-template-json","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.25.2"},{"fixed":"2.25.2-tuxcare.1"}]}],"versions":["2.25.2"],"bundled":5},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.17.0"},{"fixed":"2.17.0-tuxcare.2"}]}],"versions":["2.17.0","2.17.0-tuxcare.1"],"bundled":2},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.logging.log4j:log4j-layout-template-json","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.17.0"},{"fixed":"2.17.0-tuxcare.2"}]}],"versions":["2.17.0","2.17.0-tuxcare.1"],"bundled":2},{"source":"osv","ecosystem":"Debian:12","package":"apache-log4j2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.19.0-2","2.26.1-1"]},{"source":"osv","ecosystem":"Debian:13","package":"apache-log4j2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.19.0-2","2.26.1-1"]},{"source":"osv","ecosystem":"Debian:14","package":"apache-log4j2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.19.0-2","2.26.1-1"]},{"source":"osv","ecosystem":"Maven","package":"org.apache.logging.log4j:log4j-layout-template-json","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.14.0"},{"fixed":"2.25.4"}]}],"versions":["2.14.0","2.14.1","2.15.0","2.16.0","2.17.0","2.17.1","2.17.2","2.18.0","2.19.0","2.20.0","2.21.0","2.21.1","2.22.0","2.22.1","2.23.0","2.23.1","2.24.0","2.24.1","2.24.2","2.24.3","2.25.0","2.25.1","2.25.2","2.25.3"]},{"source":"osv","ecosystem":"Maven","package":"org.apache.logging.log4j:log4j-layout-template-json","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0-alpha1"},{"last_affected":"3.0.0-beta3"}]}],"versions":["3.0.0-alpha1","3.0.0-beta1","3.0.0-beta2","3.0.0-beta3"]},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"log4j","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.17.2-2.oe2403sp1"}]}],"bundled":2},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP3","package":"log4j","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.17.2-2.oe2403sp3"}]}],"bundled":2},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP4","package":"log4j","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.17.2-2.oe2403sp4"}]}],"bundled":2},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP4","package":"log4j","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.17.0-5.oe2003sp4"}]}],"bundled":2},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP4","package":"log4j","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.17.2-2.oe2203sp4"}]}],"bundled":2},{"source":"osv","ecosystem":"Root:Maven","package":"org.apache.logging.log4j:log4j-layout-template-json","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.23.1-aikido.2"},{"fixed":"2.21.1-aikido.5"},{"fixed":"2.23.1-aikido.3"},{"fixed":"2.24.3-aikido.1"}]}]},{"source":"osv","ecosystem":"Root:Maven","package":"io.root.org.apache.logging.log4j:log4j-layout-template-json","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.23.1-root.io.1"},{"fixed":"2.21.1-root.io.1"},{"fixed":"2.23.1-root.io.2"},{"fixed":"2.21.1-root.io.4"},{"fixed":"2.21.1-root.io.5"},{"fixed":"2.23.1-root.io.3"},{"fixed":"2.24.3-root.io.1"}]}]},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"apache-log4j1.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.2.17-3ubuntu1","1.2.17-4ubuntu1","1.2.17-4ubuntu2","1.2.17-4ubuntu3","1.2.17-4ubuntu3+esm1","1.2.17-4ubuntu3+esm2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"apache-log4j2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.2-1","2.4-1","2.4-2","2.4-2ubuntu0.1~esm1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"apache-log4j1.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.2.17-6ubuntu1","1.2.17-7ubuntu1","1.2.17-7ubuntu1+esm1","1.2.17-7ubuntu1+esm2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"apache-log4j1.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.2.17-7ubuntu2","1.2.17-8","1.2.17-8+deb10u1build0.18.04.1","1.2.17-8+deb10u1ubuntu0.1","1.2.17-8+deb10u1ubuntu0.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"apache-log4j2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.8.2-1","2.8.2-2","2.10.0-1","2.10.0-2","2.10.0-2ubuntu0.1","2.12.4-0ubuntu0.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"apache-log4j1.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.2.17-8","1.2.17-9","1.2.17-9ubuntu0.1","1.2.17-9ubuntu0.2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"apache-log4j2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.11.1-2","2.11.2-1","2.15.0-0.20.04.1","2.16.0-0.20.04.1","2.17.0-0.20.04.1","2.17.1-0.20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"apache-log4j1.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.2.17-10","1.2.17-11"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"apache-log4j2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.13.3-1","2.15.0-1","2.16.0-1","2.17.0-1","2.17.1-1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"apache-log4j1.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.2.17-11"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"apache-log4j2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.19.0-2"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"apache-log4j1.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.2.17-11"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"apache-log4j2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.19.0-2"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"apache-log4j1.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.2.17-11build1"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"apache-log4j2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.19.0-2build1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"apache-log4j1.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.2.17-11","1.2.17-11build1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"apache-log4j2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.19.0-2","2.19.0-2build1"]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"log4j","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.20.0-2.1"}]}],"bundled":4}],"products":[{"vendor":"apache","product":"log4j"},{"vendor":"apache software foundation","product":"apache log4j json template layout"}],"references":[{"url":"https://github.com/apache/logging-log4j2/pull/4080","tags":["patch","Issue Tracking","fix","web","report"]},{"url":"https://logging.apache.org/security.html#CVE-2026-34481","tags":["vendor-advisory","Vendor Advisory","advisory","web","report"]},{"url":"https://logging.apache.org/cyclonedx/vdr.xml","tags":["vendor-advisory","Product","advisory","web","report"]},{"url":"https://logging.apache.org/log4j/2.x/manual/json-template-layout.html","tags":["related","Technical Description","web","report"]},{"url":"https://lists.apache.org/thread/n34zdv00gbkdbzt2rx9rf5mqz6lhopcv","tags":["vendor-advisory","Mailing List","Vendor Advisory","advisory","web","report"]},{"url":"http://www.openwall.com/lists/oss-security/2026/04/10/10","tags":["Mailing List","Third Party Advisory","web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-34481","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-w35j-pv5h-q9q9"},{"url":"https://repo.maven.apache.org/maven2","tags":["web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/34xxx/CVE-2026-34481.json","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-34481","tags":["advisory"]},{"url":"https://github.com/apache/logging-log4j2","tags":["package"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3153","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-49844","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20261843-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1262050","tags":["report"]},{"url":"https://bugzilla.suse.com/1262091","tags":["report"]},{"url":"https://bugzilla.suse.com/1262092","tags":["report"]},{"url":"https://bugzilla.suse.com/1262093","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2026-34477","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-34479","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-34480","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-34481","tags":["web"]},{"url":"https://ubuntu.com/security/CVE-2026-34481","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-34481","tags":["report"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-34481","title":"Apache Log4j JSON Template Layout: Improper serialization of non-finite floating-point values in JsonTemplateLayout","description":"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.\n\nAn attacker can exploit this issue only if both of the following conditions are met:\n\n  *  The application uses JsonTemplateLayout.\n  *  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.\n\n\nUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.\n\nNote: 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":"published","published":"2026-04-10T15:43:00.1Z","modified":"2026-07-11T04:55:42.502Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N","level":"medium","assessor":"cna"}],"cwes":["CWE-116"],"updated_at":"2026-11-02T14:20:14.302133Z"}],"euvd":[{"id":"EUVD-2026-21412","description":"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.\n\nAn attacker can exploit this issue only if both of the following conditions are met:\n\n  *  The application uses JsonTemplateLayout.\n  *  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.\n\n\nUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.\n\nNote: 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":"published","published":"2026-04-10T15:43:00Z","modified":"2026-07-11T04:55:42Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N","level":"medium"}],"updated_at":"2026-11-02T18:20:02.308684Z"}],"ghsa":[{"id":"GHSA-w35j-pv5h-q9q9","title":"Apache Log4j JSON Template Layout: Improper serialization of non-finite floating-point values in JsonTemplateLayout","description":"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.\n\nAn attacker can exploit this issue only if both of the following conditions are met:\n\n  *  The application uses `JsonTemplateLayout`.\n  *  The application logs a `MapMessage` containing an attacker-controlled floating-point value.\n\nUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.","status":"published","published":"2026-04-10T18:31:18Z","modified":"2026-04-13T23:59:43Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N","level":"medium"}],"cwes":["CWE-116"],"updated_at":"2026-11-02T14:39:53.087746Z"}],"nvd":[{"id":"CVE-2026-34481","description":"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.\n\nAn attacker can exploit this issue only if both of the following conditions are met:\n\n  *  The application uses JsonTemplateLayout.\n  *  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.\n\n\nUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.\n\nNote: 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":"published","published":"2026-04-10T16:16:31.663Z","modified":"2026-10-26T22:10:00.163Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"medium","assessor":"secondary"},{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high","assessor":"primary"}],"cwes":["CWE-116"],"updated_at":"2026-11-02T14:12:13.902911Z"}],"osv":[{"id":"CVE-2026-34481","title":"Apache Log4j JSON Template Layout: Improper serialization of non-finite floating-point values in JsonTemplateLayout","description":"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.\n\nAn attacker can exploit this issue only if both of the following conditions are met:\n\n  *  The application uses JsonTemplateLayout.\n  *  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.\n\n\nUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.\n\nNote: 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":"published","published":"2026-04-10T15:43:00.1Z","modified":"2026-10-28T02:31:01.034811421Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N","level":"medium"}],"cwes":["CWE-116"],"updated_at":"2026-11-02T15:45:02.247031Z"},{"id":"DEBIAN-CVE-2026-34481","description":"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":"published","published":"2026-04-10T16:16:31.663Z","modified":"2026-10-27T10:01:02.267322415Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:45:54.587575Z"},{"id":"GHSA-w35j-pv5h-q9q9","title":"Apache Log4j JSON Template Layout: Improper serialization of non-finite floating-point values in JsonTemplateLayout","description":"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.\n\nAn attacker can exploit this issue only if both of the following conditions are met:\n\n  *  The application uses `JsonTemplateLayout`.\n  *  The application logs a `MapMessage` containing an attacker-controlled floating-point value.\n\nUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.","status":"published","published":"2026-04-10T18:31:18Z","modified":"2026-09-10T03:51:03.622660398Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N","level":"medium"}],"cwes":["CWE-116"],"updated_at":"2026-11-02T15:46:58.04805Z"},{"id":"OESA-2026-3153","title":"log4j security update","description":"Log4j is a tool to help the programmer output log statements to a variety of output targets.\r\n\r\nSecurity Fix(es):\n\nApache Log4j\u0026apos;s JsonTemplateLayout 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: 1) The application uses JsonTemplateLayout; 2) The application logs a MapMessage containing an attacker-controlled floating-point value.(CVE-2026-34481)\n\nImproper encoding of non-finite floating-point values during MapMessage JSON serialization in Apache Log4j API produces output that is not valid JSON. This issue affects Apache Log4j API versions 2.13.1 through 2.25.4 and version 2.26.0.\n\nThe fix for CVE-2026-34481 did not cover all code paths: when a MapMessage contains a non-finite IEEE 754 value (NaN, Infinity, or -Infinity), MapMessage.asJson() emits the corresponding bare token. RFC 8259 does not permit these tokens, so a conformant parser rejects the resulting document.\n\nThe defect is reachable only when both of the following conditions hold:\n\n  *  The application uses the  message resolver https://logging.apache.org/log4j/2.x/manual/json-template-layout.html#event-template-resolver-message  of JsonTemplateLayout or any other layout that relies on MapMessage.asJson() or MapMessage.getFormattedMessage(new String[]{\u0026quot;JSON\u0026quot;}).\n  *  The application logs a MapMessage that contains an attacker-controlled floating-point value.\n\n\nAn attacker who can supply a non-finite value can cause the affected layout to emit malformed JSON, which may corrupt the enclosing log record or disrupt downstream log ingestion and parsing.\n\nUsers are advised to upgrade to Apache Log4j API 2.25.5 or 2.26.1, both of which emit RFC 8259-compliant JSON for non-finite values.(CVE-2026-49844)","status":"published","published":"2026-07-24T11:12:02Z","modified":"2026-08-18T01:21:25.309649246Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"medium"}],"updated_at":"2026-11-02T15:52:46.823443Z"},{"id":"ROOT-APP-MAVEN-CVE-2026-34481","title":"CVE-2026-34481 in org.apache.logging.log4j:log4j-layout-template-json - Patched by Root","description":"Root has patched CVE-2026-34481 in the org.apache.logging.log4j:log4j-layout-template-json package for Root:Maven. Multiple fixed versions available.","status":"published","published":"2026-09-30T12:59:11Z","modified":"2026-09-30T13:15:02.947882191Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","level":"medium"}],"updated_at":"2026-11-02T15:53:27.066589Z"},{"id":"UBUNTU-CVE-2026-34481","description":"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":"published","published":"2026-04-10T16:16:00Z","modified":"2026-10-17T13:00:02.275012133Z","cvss":[{"version":"4.0","score":6.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N","level":"medium"},{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T16:56:16.036833Z"},{"id":"CLSA-2026-1780447835","title":"TuxCare security update for org.apache.logging.log4j (3 CVEs)","description":"TuxCare rebuilt 3 org.apache.logging.log4j packages to address 3 CVEs. Fixed in 2.22.1-tuxcare.1.","status":"published","published":"2026-08-04T14:52:35Z","modified":"2026-11-02T19:45:33.874096911Z","updated_at":"2026-11-02T20:30:18.404297Z"},{"id":"CLSA-2026-1784683011","title":"TuxCare security update for org.apache.logging.log4j (2 CVEs)","description":"TuxCare rebuilt 2 org.apache.logging.log4j packages to address 2 CVEs. Fixed in 2.24.3-tuxcare.1.","status":"published","published":"2026-08-04T14:52:47Z","modified":"2026-11-02T19:45:43.426767174Z","updated_at":"2026-11-02T20:30:13.950198Z"},{"id":"CLSA-2026-1784769542","title":"TuxCare security update for org.apache.logging.log4j (2 CVEs)","description":"TuxCare rebuilt 2 org.apache.logging.log4j packages to address 2 CVEs. Fixed in 2.18.0-tuxcare.1.","status":"published","published":"2026-08-04T14:52:47Z","modified":"2026-11-02T19:45:45.378719718Z","updated_at":"2026-11-02T20:30:13.950198Z"},{"id":"CLSA-2026-1784769579","title":"TuxCare security update for org.apache.logging.log4j:log4j-layout-template-json (1 CVE)","description":"TuxCare rebuilt org.apache.logging.log4j:log4j-layout-template-json to address 1 CVE. Fixed in 2.17.1-tuxcare.3.","status":"published","published":"2026-08-04T14:52:48Z","modified":"2026-10-29T19:45:15.484086472Z","updated_at":"2026-11-02T15:43:46.482572Z"},{"id":"CLSA-2026-1785727932","title":"TuxCare security update for org.apache.logging.log4j (3 CVEs)","description":"TuxCare rebuilt 2 org.apache.logging.log4j packages to address 3 CVEs. Fixed in 2.17.2-tuxcare.2.","status":"published","published":"2026-08-04T14:52:51Z","modified":"2026-11-02T19:45:49.91461624Z","updated_at":"2026-11-02T20:30:00.884471Z"},{"id":"CLSA-2026-1787471222","title":"TuxCare security update for org.apache.logging.log4j (3 CVEs)","description":"TuxCare rebuilt 4 org.apache.logging.log4j packages to address 3 CVEs. Fixed in 2.23.1-tuxcare.1.","status":"published","published":"2026-08-23T07:47:02Z","modified":"2026-11-02T19:46:00.425131919Z","updated_at":"2026-11-02T20:29:46.576514Z"},{"id":"CLSA-2026-1790709023","title":"TuxCare security update for org.apache.logging.log4j (3 CVEs)","description":"TuxCare rebuilt 3 org.apache.logging.log4j packages to address 3 CVEs. Fixed in 2.24.1-tuxcare.1.","status":"published","published":"2026-09-29T19:10:23Z","modified":"2026-11-02T19:46:25.008231607Z","updated_at":"2026-11-02T20:29:22.637147Z"},{"id":"CLSA-2026-1790944047","title":"TuxCare security update for org.apache.logging.log4j (3 CVEs)","description":"TuxCare rebuilt 3 org.apache.logging.log4j packages to address 3 CVEs. Fixed in 2.19.0-tuxcare.1.","status":"published","published":"2026-10-02T12:27:27Z","modified":"2026-11-02T19:46:26.196653528Z","updated_at":"2026-11-02T20:29:17.805906Z"},{"id":"CLSA-2026-1792696729","title":"TuxCare security update for org.apache.logging.log4j (5 CVEs)","description":"TuxCare rebuilt 4 org.apache.logging.log4j packages to address 5 CVEs. Fixed in 2.20.0-tuxcare.2.","status":"published","published":"2026-10-22T19:18:49Z","modified":"2026-11-02T19:46:31.511807766Z","updated_at":"2026-11-02T20:28:59.01272Z"},{"id":"CLSA-2026-1793052872","title":"TuxCare security update for org.apache.logging.log4j (4 CVEs)","description":"TuxCare rebuilt 4 org.apache.logging.log4j packages to address 4 CVEs. Fixed in 2.21.1-tuxcare.1.","status":"published","published":"2026-10-26T22:14:32Z","modified":"2026-11-02T19:46:31.591611961Z","updated_at":"2026-11-02T20:28:59.01272Z"},{"id":"CLSA-2026-1793354113","title":"TuxCare security update for org.apache.logging.log4j (5 CVEs)","description":"TuxCare rebuilt 3 org.apache.logging.log4j packages to address 5 CVEs. Fixed in 2.25.2-tuxcare.1.","status":"published","published":"2026-10-30T10:55:14Z","modified":"2026-11-02T19:46:33.204047397Z","updated_at":"2026-11-02T20:28:42.34712Z"},{"id":"CLSA-2026-1793882002","title":"TuxCare security update for org.apache.logging.log4j (2 CVEs)","description":"TuxCare rebuilt 2 org.apache.logging.log4j packages to address 2 CVEs. Fixed in 2.17.0-tuxcare.2.","status":"published","published":"2026-11-05T13:33:23Z","modified":"2026-11-06T13:15:03.968364542Z","updated_at":"2026-11-06T13:44:21.739016Z"},{"id":"openSUSE-SU-2026:10544-1","title":"log4j-2.20.0-2.1 on GA media","description":"These are all security issues fixed in the log4j-2.20.0-2.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-04-14T00:00:00Z","modified":"2026-04-15T08:00:07.138921Z","updated_at":"2026-11-02T16:58:38.415593Z"},{"id":"SUSE-SU-2026:1843-1","title":"Security update for log4j","description":"This update for log4j fixes the following issues:\n\n- CVE-2026-34477: TLS connections vulnerable to interception due to incomplete hostname verification configuration\n  checks (bsc#1262050).\n- CVE-2026-34479: silent log event loss due to improper XML escaping in `Log4j1XmlLayout` (bsc#1262091).\n- CVE-2026-34480: silent log event loss due to improper XML escaping in `XmlLayout` (bsc#1262092).\n- CVE-2026-34481: silent log event loss due to improper serialization of non-finite floating-point values in\n  `JsonTemplateLayout` (bsc#1262093).\n","status":"published","published":"2026-05-13T15:24:57Z","modified":"2026-05-14T08:15:07.933753Z","updated_at":"2026-11-02T15:54:01.610851Z"}]}}