https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 19:53:34 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-00009 bdu:2026-00009 https://cve.radiocsirt.org/vuln/bdu:2026-00009 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0199 certfr-2026-avi-0199 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0199 https://cve.radiocsirt.org/vuln/cleanstart-2026-aj02810 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: kserve-modelmesh</p> <p>Package kserve-modelmesh version 0.12.0-r0 fixes 20 vulnerabilities: CVE-2026-24281, CVE-2026-24308, CVE-2026-33870, CVE-2026-33871, ghsa-7xrh-hqfc-g7qr...</p> <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: kserve-modelmesh</p> <p>Package kserve-modelmesh version 0.12.0-r0 fixes 20 vulnerabilities: CVE-2026-24281, CVE-2026-24308, CVE-2026-33870, CVE-2026-33871, ghsa-7xrh-hqfc-g7qr...</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-aj02810 https://cve.radiocsirt.org/vuln/euvd-2026-290444 EUVD-2026-290444 https://cve.radiocsirt.org/vuln/euvd-2026-290444 https://cve.radiocsirt.org/vuln/fkie_cve-2025-68161 <p>The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName configuration attribute or the log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName system property is set to true.</p> <p>This issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions:</p> <p>* The attacker is able to intercept or redirect network traffic between the client and the log receiver. * The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured).</p> <p>Users are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue.</p> <p>As an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.</p> <p>The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName configuration attribute or the log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName system property is set to true.</p> <p>This issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions:</p> <p>* The attacker is able to intercept or redirect network traffic between the client and the log receiver. * The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured).</p> <p>Users are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue.</p> <p>As an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-68161 https://cve.radiocsirt.org/vuln/ghsa-vc5p-v9hr-52mj <p><strong>Affected:</strong> Maven: org.apache.logging.log4j:log4j-core</p> <p>The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the [verifyHostName](https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName) configuration attribute or the [log4j2.sslVerifyHostName](https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName) system property is set to true.</p> <p>This issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions:</p> <p>* The attacker is able to intercept or redirect network traffic between the client and the log receiver. * The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured).</p> <p>Users are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue.</p> <p>As an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.</p> <p><strong>Affected:</strong> Maven: org.apache.logging.log4j:log4j-core</p> <p>The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the [verifyHostName](https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName) configuration attribute or the [log4j2.sslVerifyHostName](https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName) system property is set to true.</p> <p>This issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions:</p> <p>* The attacker is able to intercept or redirect network traffic between the client and the log receiver. * The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured).</p> <p>Users are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue.</p> <p>As an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.</p> https://cve.radiocsirt.org/vuln/ghsa-vc5p-v9hr-52mj https://cve.radiocsirt.org/vuln/msrc_cve-2025-68161 msrc_CVE-2025-68161 https://cve.radiocsirt.org/vuln/msrc_cve-2025-68161 https://cve.radiocsirt.org/vuln/ncsc-2026-0021 NCSC-2026-0021 https://cve.radiocsirt.org/vuln/ncsc-2026-0021 https://cve.radiocsirt.org/vuln/opensuse-su-2026:10009-1 <p>log4j-2.20.0-1.1 on GA media</p> <p>log4j-2.20.0-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:10009-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68161 <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: apache-log4j2, Ubuntu:18.04:LTS: apache-log4j2, Ubuntu:20.04:LTS: apache-log4j2, Ubuntu:22.04:LTS: apache-log4j2, Ubuntu:24.04:LTS: apache-log4j2, Ubuntu:25.10: apache-log4j2, Ubuntu:26.04:LTS: apache-log4j2</p> <p>The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName configuration attribute or the log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName system property is set to true. This issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions: * The attacker is able to intercept or redirect network traffic between the client and the log receiver. * The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured). Users are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue. As an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.</p> <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: apache-log4j2, Ubuntu:18.04:LTS: apache-log4j2, Ubuntu:20.04:LTS: apache-log4j2, Ubuntu:22.04:LTS: apache-log4j2, Ubuntu:24.04:LTS: apache-log4j2, Ubuntu:25.10: apache-log4j2, Ubuntu:26.04:LTS: apache-log4j2</p> <p>The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName configuration attribute or the log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName system property is set to true. This issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions: * The attacker is able to intercept or redirect network traffic between the client and the log receiver. * The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured). Users are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue. As an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68161 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2897 <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Apache log4j ausnutzen, um Informationen offenzulegen.</p> <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Apache log4j ausnutzen, um Informationen offenzulegen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2897