{"schema_version":"1.7.2","id":"OESA-2026-3153","modified":"2026-07-24T03:27:58Z","published":"2026-07-24T03:27:58Z","upstream":["CVE-2026-34481","CVE-2026-49844"],"summary":"log4j security update","details":"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'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[]{"JSON"}).\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)","affected":[{"package":{"ecosystem":"openEuler:24.03-LTS-SP1","name":"log4j","purl":"pkg:rpm/openEuler/log4j&distro=openEuler-24.03-LTS-SP1"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.17.2-2.oe2403sp1"}]}],"ecosystem_specific":{"noarch":["log4j-2.17.2-2.oe2403sp1.noarch.rpm","log4j-bom-2.17.2-2.oe2403sp1.noarch.rpm","log4j-help-2.17.2-2.oe2403sp1.noarch.rpm","log4j-jcl-2.17.2-2.oe2403sp1.noarch.rpm","log4j-jmx-gui-2.17.2-2.oe2403sp1.noarch.rpm","log4j-slf4j-2.17.2-2.oe2403sp1.noarch.rpm","log4j-taglib-2.17.2-2.oe2403sp1.noarch.rpm","log4j-web-2.17.2-2.oe2403sp1.noarch.rpm"],"src":["log4j-2.17.2-2.oe2403sp1.src.rpm"]}},{"package":{"ecosystem":"openEuler:24.03-LTS-SP3","name":"log4j","purl":"pkg:rpm/openEuler/log4j&distro=openEuler-24.03-LTS-SP3"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.17.2-2.oe2403sp3"}]}],"ecosystem_specific":{"noarch":["log4j-2.17.2-2.oe2403sp3.noarch.rpm","log4j-bom-2.17.2-2.oe2403sp3.noarch.rpm","log4j-help-2.17.2-2.oe2403sp3.noarch.rpm","log4j-jcl-2.17.2-2.oe2403sp3.noarch.rpm","log4j-jmx-gui-2.17.2-2.oe2403sp3.noarch.rpm","log4j-slf4j-2.17.2-2.oe2403sp3.noarch.rpm","log4j-taglib-2.17.2-2.oe2403sp3.noarch.rpm","log4j-web-2.17.2-2.oe2403sp3.noarch.rpm"],"src":["log4j-2.17.2-2.oe2403sp3.src.rpm"]}},{"package":{"ecosystem":"openEuler:24.03-LTS-SP4","name":"log4j","purl":"pkg:rpm/openEuler/log4j&distro=openEuler-24.03-LTS-SP4"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.17.2-2.oe2403sp4"}]}],"ecosystem_specific":{"noarch":["log4j-2.17.2-2.oe2403sp4.noarch.rpm","log4j-bom-2.17.2-2.oe2403sp4.noarch.rpm","log4j-help-2.17.2-2.oe2403sp4.noarch.rpm","log4j-jcl-2.17.2-2.oe2403sp4.noarch.rpm","log4j-jmx-gui-2.17.2-2.oe2403sp4.noarch.rpm","log4j-slf4j-2.17.2-2.oe2403sp4.noarch.rpm","log4j-taglib-2.17.2-2.oe2403sp4.noarch.rpm","log4j-web-2.17.2-2.oe2403sp4.noarch.rpm"],"src":["log4j-2.17.2-2.oe2403sp4.src.rpm"]}},{"package":{"ecosystem":"openEuler:20.03-LTS-SP4","name":"log4j","purl":"pkg:rpm/openEuler/log4j&distro=openEuler-20.03-LTS-SP4"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.17.0-5.oe2003sp4"}]}],"ecosystem_specific":{"noarch":["log4j-2.17.0-5.oe2003sp4.noarch.rpm","log4j-bom-2.17.0-5.oe2003sp4.noarch.rpm","log4j-help-2.17.0-5.oe2003sp4.noarch.rpm","log4j-jcl-2.17.0-5.oe2003sp4.noarch.rpm","log4j-jmx-gui-2.17.0-5.oe2003sp4.noarch.rpm","log4j-slf4j-2.17.0-5.oe2003sp4.noarch.rpm","log4j-taglib-2.17.0-5.oe2003sp4.noarch.rpm","log4j-web-2.17.0-5.oe2003sp4.noarch.rpm"],"src":["log4j-2.17.0-5.oe2003sp4.src.rpm"]}},{"package":{"ecosystem":"openEuler:22.03-LTS-SP4","name":"log4j","purl":"pkg:rpm/openEuler/log4j&distro=openEuler-22.03-LTS-SP4"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.17.2-2.oe2203sp4"}]}],"ecosystem_specific":{"noarch":["log4j-2.17.2-2.oe2203sp4.noarch.rpm","log4j-bom-2.17.2-2.oe2203sp4.noarch.rpm","log4j-help-2.17.2-2.oe2203sp4.noarch.rpm","log4j-jcl-2.17.2-2.oe2203sp4.noarch.rpm","log4j-jmx-gui-2.17.2-2.oe2203sp4.noarch.rpm","log4j-slf4j-2.17.2-2.oe2203sp4.noarch.rpm","log4j-taglib-2.17.2-2.oe2203sp4.noarch.rpm","log4j-web-2.17.2-2.oe2203sp4.noarch.rpm"],"src":["log4j-2.17.2-2.oe2203sp4.src.rpm"]}}],"references":[{"type":"ADVISORY","url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3153"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-34481"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-49844"}],"database_specific":{"severity":"Medium"}}