https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-02T19:52:12.436834+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2026-00009 bdu:2026-00009 2026-10-02T19:52:12.772390+00:00 bdu:2026-00009 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0199 certfr-2026-avi-0199 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Certaines d'entre elles permettent à un attaq… 2026-10-02T19:52:12.772453+00:00 certfr-2026-avi-0199 https://cve.radiocsirt.org/vuln/cleanstart-2026-aj02810 Withdrawn: CLEANSTART-2026-AJ02810 — Security fixes in kserve-modelmesh 0.12.0-r0 2026-10-02T19:52:12.772494+00:00

Withdrawn by the publisher.

Affected: CleanStart: kserve-modelmesh

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...

 https://cve.radiocsirt.org/vuln/euvd-2026-290444 EUVD-2026-290444 2026-10-02T19:52:12.772543+00:00 EUVD-2026-290444 https://cve.radiocsirt.org/vuln/fkie_cve-2025-68161 fkie_cve-2025-68161 2026-10-02T19:52:12.772564+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-vc5p-v9hr-52mj GHSA-vc5p-v9hr-52mj — Apache Log4j does not verify the TLS hostname in its Socket Appender 2026-10-02T19:52:12.772632+00:00

Affected: Maven: org.apache.logging.log4j:log4j-core

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.

 https://cve.radiocsirt.org/vuln/msrc_cve-2025-68161 msrc_CVE-2025-68161 — Apache Log4j Core: Missing TLS hostname verification in Socket appender 2026-10-02T19:52:12.772698+00:00 msrc_CVE-2025-68161 https://cve.radiocsirt.org/vuln/ncsc-2026-0021 NCSC-2026-0021 — Kwetsbaarheden verholpen in Oracle Database Server producten 2026-10-02T19:52:12.772724+00:00 NCSC-2026-0021 https://cve.radiocsirt.org/vuln/opensuse-su-2026:10009-1 openSUSE-SU-2026:10009-1 — log4j-2.20.0-1.1 on GA media 2026-10-02T19:52:12.772796+00:00

log4j-2.20.0-1.1 on GA media

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68161 UBUNTU-CVE-2025-68161 2026-10-02T19:52:12.772822+00:00

Affected: 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

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.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2897 WID-SEC-W-2025-2897 — Apache log4j: Schwachstelle ermöglicht Offenlegung von Informationen 2026-10-02T19:52:12.772899+00:00

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Apache log4j ausnutzen, um Informationen offenzulegen.