https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 14:30:28 +0000 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0920 certfr-2026-avi-0920 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0920 https://cve.radiocsirt.org/vuln/cleanstart-2026-cg99434 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: solr</p> <p>Multiple security vulnerabilities affect the solr package. These issues are resolved in later releases. See references for individual vulnerability details.</p> <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: solr</p> <p>Multiple security vulnerabilities affect the solr package. These issues are resolved in later releases. See references for individual vulnerability details.</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-cg99434 https://cve.radiocsirt.org/vuln/euvd-2026-335773 EUVD-2026-335773 https://cve.radiocsirt.org/vuln/euvd-2026-335773 https://cve.radiocsirt.org/vuln/fkie_cve-2026-34481 <p>Apache Log4j&#39;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.</p> <p>An attacker can exploit this issue only if both of the following conditions are met:</p> <p>* 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.</p> <p>Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.</p> <p>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.</p> <p>Apache Log4j&#39;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.</p> <p>An attacker can exploit this issue only if both of the following conditions are met:</p> <p>* 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.</p> <p>Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-34481 https://cve.radiocsirt.org/vuln/ghsa-w35j-pv5h-q9q9 <p><strong>Affected:</strong> Maven: org.apache.logging.log4j:log4j-layout-template-json</p> <p>Apache Log4j&#39;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.</p> <p>An attacker can exploit this issue only if both of the following conditions are met:</p> <p>* The application uses `JsonTemplateLayout`. * The application logs a `MapMessage` containing an attacker-controlled floating-point value.</p> <p>Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.</p> <p><strong>Affected:</strong> Maven: org.apache.logging.log4j:log4j-layout-template-json</p> <p>Apache Log4j&#39;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.</p> <p>An attacker can exploit this issue only if both of the following conditions are met:</p> <p>* The application uses `JsonTemplateLayout`. * The application logs a `MapMessage` containing an attacker-controlled floating-point value.</p> <p>Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.</p> https://cve.radiocsirt.org/vuln/ghsa-w35j-pv5h-q9q9 https://cve.radiocsirt.org/vuln/msrc_cve-2026-34481 msrc_CVE-2026-34481 https://cve.radiocsirt.org/vuln/msrc_cve-2026-34481 https://cve.radiocsirt.org/vuln/ncsc-2026-0200 NCSC-2026-0200 https://cve.radiocsirt.org/vuln/ncsc-2026-0200 https://cve.radiocsirt.org/vuln/oesa-2026-3153 <p><strong>Affected:</strong> openEuler:24.03-LTS-SP1: log4j, openEuler:24.03-LTS-SP3: log4j, openEuler:24.03-LTS-SP4: log4j, openEuler:20.03-LTS-SP4: log4j, openEuler:22.03-LTS-SP4: log4j</p> <p>Log4j is a tool to help the programmer output log statements to a variety of output targets. Security Fix(es):</p> <p>Apache Log4j&amp;apos;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)</p> <p>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.</p> <p>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.</p> <p>The defect is reachable only when both of the following conditions hold:</p> <p>* 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 MapMess…</p> <p><strong>Affected:</strong> openEuler:24.03-LTS-SP1: log4j, openEuler:24.03-LTS-SP3: log4j, openEuler:24.03-LTS-SP4: log4j, openEuler:20.03-LTS-SP4: log4j, openEuler:22.03-LTS-SP4: log4j</p> <p>Log4j is a tool to help the programmer output log statements to a variety of output targets. Security Fix(es):</p> <p>Apache Log4j&amp;apos;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)</p> <p>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.</p> <p>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.</p> <p>The defect is reachable only when both of the following conditions hold:</p> <p>* 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 MapMess…</p> https://cve.radiocsirt.org/vuln/oesa-2026-3153 https://cve.radiocsirt.org/vuln/opensuse-su-2026:10544-1 <p>log4j-2.20.0-2.1 on GA media</p> <p>log4j-2.20.0-2.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:10544-1 https://cve.radiocsirt.org/vuln/rhsa-2026:21773 <p>org.eclipse.jetty/jetty-http: org.eclipse.jetty: Security bypass due to differential URI parsing org.eclipse.jetty/jetty-http: HTTP request smuggling via chunked extension quoted-string parsing org.apache.logging.log4j/log4j-core: Apache Log4j Core: Man-in-the-middle attack due to incomplete hostname verification org.apache.logging.log4j/log4j-core: Apache Log4j Core: Log injection via CRLF sequences due to configuration attribute renames org.apache.logging.log4j/log4j-1.2-api: Apache Log4j 1-to-Log4j 2 bridge: Log processing denial of service due to improper XML escaping org.apache.logging.log4j/log4j-core: Apache Log4j Core: Invalid XML output causes denial of service in logging org.apache.logging.log4j: Apache Log4j JsonTemplateLayout: Denial of Service via invalid JSON output</p> <p>org.eclipse.jetty/jetty-http: org.eclipse.jetty: Security bypass due to differential URI parsing org.eclipse.jetty/jetty-http: HTTP request smuggling via chunked extension quoted-string parsing org.apache.logging.log4j/log4j-core: Apache Log4j Core: Man-in-the-middle attack due to incomplete hostname verification org.apache.logging.log4j/log4j-core: Apache Log4j Core: Log injection via CRLF sequences due to configuration attribute renames org.apache.logging.log4j/log4j-1.2-api: Apache Log4j 1-to-Log4j 2 bridge: Log processing denial of service due to improper XML escaping org.apache.logging.log4j/log4j-core: Apache Log4j Core: Invalid XML output causes denial of service in logging org.apache.logging.log4j: Apache Log4j JsonTemplateLayout: Denial of Service via invalid JSON output</p> https://cve.radiocsirt.org/vuln/rhsa-2026:21773 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-34481 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: apache-log4j1.2, Ubuntu:Pro:16.04:LTS: apache-log4j2, Ubuntu:Pro:16.04:LTS: apache-log4j1.2, Ubuntu:18.04:LTS: apache-log4j1.2, Ubuntu:18.04:LTS: apache-log4j2, Ubuntu:20.04:LTS: apache-log4j1.2, Ubuntu:20.04:LTS: apache-log4j2, Ubuntu:22.04:LTS: apache-log4j1.2, Ubuntu:22.04:LTS: apache-log4j2, Ubuntu:24.04:LTS: apache-log4j1.2 and 5 more</p> <p>Apache Log4j&#39;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.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: apache-log4j1.2, Ubuntu:Pro:16.04:LTS: apache-log4j2, Ubuntu:Pro:16.04:LTS: apache-log4j1.2, Ubuntu:18.04:LTS: apache-log4j1.2, Ubuntu:18.04:LTS: apache-log4j2, Ubuntu:20.04:LTS: apache-log4j1.2, Ubuntu:20.04:LTS: apache-log4j2, Ubuntu:22.04:LTS: apache-log4j1.2, Ubuntu:22.04:LTS: apache-log4j2, Ubuntu:24.04:LTS: apache-log4j1.2 and 5 more</p> <p>Apache Log4j&#39;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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-34481 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1067 <p>Ein Angreifer kann mehrere Schwachstellen in Apache log4j ausnutzen, um Dateien zu manipulieren.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Apache log4j ausnutzen, um Dateien zu manipulieren.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1067