An update for log4j is now available for openEuler-24.03-LTS-SP1,openEuler-24.03-LTS-SP3,openEuler-24.03-LTS-SP4,openEuler-20.03-LTS-SP4,openEuler-22.03-LTS-SP4 Security Advisory openeuler-security@openeuler.org openEuler security committee openEuler-SA-2026-3153 Final 1.0 1.0 2026-07-24 Initial 2026-07-24 2026-07-24 openEuler SA Tool V1.0 2026-07-24 log4j security update An update for log4j is now available for openEuler-24.03-LTS-SP1,openEuler-24.03-LTS-SP3,openEuler-24.03-LTS-SP4,openEuler-20.03-LTS-SP4,openEuler-22.03-LTS-SP4 Log4j is a tool to help the programmer output log statements to a variety of output targets. Security Fix(es): Apache 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) Improper 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. The 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. The defect is reachable only when both of the following conditions hold: * 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"}). * The application logs a MapMessage that contains an attacker-controlled floating-point value. An 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. Users 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) An update for log4j is now available for openEuler-24.03-LTS-SP1,openEuler-24.03-LTS-SP3,openEuler-24.03-LTS-SP4,openEuler-20.03-LTS-SP4,openEuler-22.03-LTS-SP4. openEuler Security has rated this update as having a security impact of medium. A Common Vunlnerability Scoring System(CVSS)base score,which gives a detailed severity rating, is available for each vulnerability from the CVElink(s) in the References section. Medium log4j https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3153 https://www.openeuler.org/en/security/cve/detail/?cveId=CVE-2026-34481 https://www.openeuler.org/en/security/cve/detail/?cveId=CVE-2026-49844 https://nvd.nist.gov/vuln/detail/CVE-2026-34481 https://nvd.nist.gov/vuln/detail/CVE-2026-49844 openEuler-24.03-LTS-SP1 openEuler-24.03-LTS-SP3 openEuler-24.03-LTS-SP4 openEuler-20.03-LTS-SP4 openEuler-22.03-LTS-SP4 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 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 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 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 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 log4j-2.17.2-2.oe2403sp1.src.rpm log4j-2.17.2-2.oe2403sp3.src.rpm log4j-2.17.2-2.oe2403sp4.src.rpm log4j-2.17.0-5.oe2003sp4.src.rpm log4j-2.17.2-2.oe2203sp4.src.rpm Apache 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. 2026-07-24 CVE-2026-34481 openEuler-24.03-LTS-SP1 openEuler-24.03-LTS-SP3 openEuler-24.03-LTS-SP4 openEuler-20.03-LTS-SP4 openEuler-22.03-LTS-SP4 Medium 6.3 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 log4j security update 2026-07-24 https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3153 Improper 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. The 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. The defect is reachable only when both of the following conditions hold: * 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"}). * The application logs a MapMessage that contains an attacker-controlled floating-point value. An 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. Users 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. 2026-07-24 CVE-2026-49844 openEuler-24.03-LTS-SP1 openEuler-24.03-LTS-SP3 openEuler-24.03-LTS-SP4 openEuler-20.03-LTS-SP4 openEuler-22.03-LTS-SP4 Medium 6.3 AV:N/AC:L/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 log4j security update 2026-07-24 https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3153