https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 12:56:49 +0000 https://cve.radiocsirt.org/vuln/alsa-2025:1330 <p><strong>Affected:</strong> AlmaLinux:9: openssl, AlmaLinux:9: openssl-devel, AlmaLinux:9: openssl-libs, AlmaLinux:9: openssl-perl</p> <p>OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library.</p> <p>Security Fix(es):</p> <p>* openssl: RFC7250 handshakes with unauthenticated servers don&#39;t abort as expected (CVE-2024-12797)</p> <p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p> <p><strong>Affected:</strong> AlmaLinux:9: openssl, AlmaLinux:9: openssl-devel, AlmaLinux:9: openssl-libs, AlmaLinux:9: openssl-perl</p> <p>OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library.</p> <p>Security Fix(es):</p> <p>* openssl: RFC7250 handshakes with unauthenticated servers don&#39;t abort as expected (CVE-2024-12797)</p> <p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p> https://cve.radiocsirt.org/vuln/alsa-2025:1330 https://cve.radiocsirt.org/vuln/bdu:2025-01602 bdu:2025-01602 https://cve.radiocsirt.org/vuln/bdu:2025-01602 https://cve.radiocsirt.org/vuln/bell-cve-2024-12797 <p><strong>Affected:</strong> Alpaquita:stream: openssl, BellSoft Hardened Containers:stream: openssl</p> <p><strong>Affected:</strong> Alpaquita:stream: openssl, BellSoft Hardened Containers:stream: openssl</p> https://cve.radiocsirt.org/vuln/bell-cve-2024-12797 https://cve.radiocsirt.org/vuln/brew-azure-cli-cve-2024-12797 <p><strong>Affected:</strong> Homebrew: azure-cli</p> <p>pyca/cryptography&#39;s wheels include a statically linked copy of OpenSSL. The versions of OpenSSL included in cryptography 42.0.0-44.0.0 are vulnerable to a security issue. More details about the vulnerability itself can be found in https://openssl-library.org/news/secadv/20250211.txt.</p> <p>If you are building cryptography source (&#34;sdist&#34;) then you are responsible for upgrading your copy of OpenSSL. Only users installing from wheels built by the cryptography project (i.e., those distributed on PyPI) need to update their cryptography versions.</p> <p><strong>Affected:</strong> Homebrew: azure-cli</p> <p>pyca/cryptography&#39;s wheels include a statically linked copy of OpenSSL. The versions of OpenSSL included in cryptography 42.0.0-44.0.0 are vulnerable to a security issue. More details about the vulnerability itself can be found in https://openssl-library.org/news/secadv/20250211.txt.</p> <p>If you are building cryptography source (&#34;sdist&#34;) then you are responsible for upgrading your copy of OpenSSL. Only users installing from wheels built by the cryptography project (i.e., those distributed on PyPI) need to update their cryptography versions.</p> https://cve.radiocsirt.org/vuln/brew-azure-cli-cve-2024-12797 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0129 certfr-2025-avi-0129 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0129 https://cve.radiocsirt.org/vuln/cleanstart-2026-an24336 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: airflow-2</p> <p>Multiple security vulnerabilities affect the airflow-2 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: airflow-2</p> <p>Multiple security vulnerabilities affect the airflow-2 package. These issues are resolved in later releases. See references for individual vulnerability details.</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-an24336 https://cve.radiocsirt.org/vuln/euvd-2026-217837 EUVD-2026-217837 https://cve.radiocsirt.org/vuln/euvd-2026-217837 https://cve.radiocsirt.org/vuln/fkie_cve-2024-12797 <p>Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don&#39;t abort as expected when the SSL_VERIFY_PEER verification mode is set.</p> <p>Impact summary: TLS and DTLS connections using raw public keys may be vulnerable to man-in-middle attacks when server authentication failure is not detected by clients.</p> <p>RPKs are disabled by default in both TLS clients and TLS servers. The issue only arises when TLS clients explicitly enable RPK use by the server, and the server, likewise, enables sending of an RPK instead of an X.509 certificate chain. The affected clients are those that then rely on the handshake to fail when the server&#39;s RPK fails to match one of the expected public keys, by setting the verification mode to SSL_VERIFY_PEER.</p> <p>Clients that enable server-side raw public keys can still find out that raw public key verification failed by calling SSL_get_verify_result(), and those that do, and take appropriate action, are not affected. This issue was introduced in the initial implementation of RPK support in OpenSSL 3.2.</p> <p>The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.</p> <p>Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don&#39;t abort as expected when the SSL_VERIFY_PEER verification mode is set.</p> <p>Impact summary: TLS and DTLS connections using raw public keys may be vulnerable to man-in-middle attacks when server authentication failure is not detected by clients.</p> <p>RPKs are disabled by default in both TLS clients and TLS servers. The issue only arises when TLS clients explicitly enable RPK use by the server, and the server, likewise, enables sending of an RPK instead of an X.509 certificate chain. The affected clients are those that then rely on the handshake to fail when the server&#39;s RPK fails to match one of the expected public keys, by setting the verification mode to SSL_VERIFY_PEER.</p> <p>Clients that enable server-side raw public keys can still find out that raw public key verification failed by calling SSL_get_verify_result(), and those that do, and take appropriate action, are not affected. This issue was introduced in the initial implementation of RPK support in OpenSSL 3.2.</p> <p>The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-12797 https://cve.radiocsirt.org/vuln/ghsa-79v4-65xg-pq4g <p><strong>Affected:</strong> PyPI: cryptography</p> <p>pyca/cryptography&#39;s wheels include a statically linked copy of OpenSSL. The versions of OpenSSL included in cryptography 42.0.0-44.0.0 are vulnerable to a security issue. More details about the vulnerability itself can be found in https://openssl-library.org/news/secadv/20250211.txt.</p> <p>If you are building cryptography source (&#34;sdist&#34;) then you are responsible for upgrading your copy of OpenSSL. Only users installing from wheels built by the cryptography project (i.e., those distributed on PyPI) need to update their cryptography versions.</p> <p><strong>Affected:</strong> PyPI: cryptography</p> <p>pyca/cryptography&#39;s wheels include a statically linked copy of OpenSSL. The versions of OpenSSL included in cryptography 42.0.0-44.0.0 are vulnerable to a security issue. More details about the vulnerability itself can be found in https://openssl-library.org/news/secadv/20250211.txt.</p> <p>If you are building cryptography source (&#34;sdist&#34;) then you are responsible for upgrading your copy of OpenSSL. Only users installing from wheels built by the cryptography project (i.e., those distributed on PyPI) need to update their cryptography versions.</p> https://cve.radiocsirt.org/vuln/ghsa-79v4-65xg-pq4g https://cve.radiocsirt.org/vuln/msrc_cve-2024-12797 msrc_CVE-2024-12797 https://cve.radiocsirt.org/vuln/msrc_cve-2024-12797 https://cve.radiocsirt.org/vuln/opensuse-su-2025:14802-1 <p>libopenssl-3-devel-3.2.4-1.1 on GA media</p> <p>libopenssl-3-devel-3.2.4-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:14802-1 https://cve.radiocsirt.org/vuln/pysec-2026-1284 <p><strong>Affected:</strong> PyPI: cryptography</p> <p>pyca/cryptography&#39;s wheels include a statically linked copy of OpenSSL. The versions of OpenSSL included in cryptography 42.0.0-44.0.0 are vulnerable to a security issue. More details about the vulnerability itself can be found in https://openssl-library.org/news/secadv/20250211.txt.</p> <p>If you are building cryptography source (&#34;sdist&#34;) then you are responsible for upgrading your copy of OpenSSL. Only users installing from wheels built by the cryptography project (i.e., those distributed on PyPI) need to update their cryptography versions.</p> <p><strong>Affected:</strong> PyPI: cryptography</p> <p>pyca/cryptography&#39;s wheels include a statically linked copy of OpenSSL. The versions of OpenSSL included in cryptography 42.0.0-44.0.0 are vulnerable to a security issue. More details about the vulnerability itself can be found in https://openssl-library.org/news/secadv/20250211.txt.</p> <p>If you are building cryptography source (&#34;sdist&#34;) then you are responsible for upgrading your copy of OpenSSL. Only users installing from wheels built by the cryptography project (i.e., those distributed on PyPI) need to update their cryptography versions.</p> https://cve.radiocsirt.org/vuln/pysec-2026-1284 https://cve.radiocsirt.org/vuln/rhba-2025:6314 <p>openssl: RFC7250 handshakes with unauthenticated servers don&#39;t abort as expected</p> <p>openssl: RFC7250 handshakes with unauthenticated servers don&#39;t abort as expected</p> https://cve.radiocsirt.org/vuln/rhba-2025:6314 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-12797 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> Ubuntu:25.04: openssl</p> <p>Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don&#39;t abort as expected when the SSL_VERIFY_PEER verification mode is set. Impact summary: TLS and DTLS connections using raw public keys may be vulnerable to man-in-middle attacks when server authentication failure is not detected by clients. RPKs are disabled by default in both TLS clients and TLS servers. The issue only arises when TLS clients explicitly enable RPK use by the server, and the server, likewise, enables sending of an RPK instead of an X.509 certificate chain. The affected clients are those that then rely on the handshake to fail when the server&#39;s RPK fails to match one of the expected public keys, by setting the verification mode to SSL_VERIFY_PEER. Clients that enable server-side raw public keys can still find out that raw public key verification failed by calling SSL_get_verify_result(), and those that do, and take appropriate action, are not affected. This issue was introduced in the initial implementation of RPK support in OpenSSL 3.2. The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.</p> <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> Ubuntu:25.04: openssl</p> <p>Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don&#39;t abort as expected when the SSL_VERIFY_PEER verification mode is set. Impact summary: TLS and DTLS connections using raw public keys may be vulnerable to man-in-middle attacks when server authentication failure is not detected by clients. RPKs are disabled by default in both TLS clients and TLS servers. The issue only arises when TLS clients explicitly enable RPK use by the server, and the server, likewise, enables sending of an RPK instead of an X.509 certificate chain. The affected clients are those that then rely on the handshake to fail when the server&#39;s RPK fails to match one of the expected public keys, by setting the verification mode to SSL_VERIFY_PEER. Clients that enable server-side raw public keys can still find out that raw public key verification failed by calling SSL_get_verify_result(), and those that do, and take appropriate action, are not affected. This issue was introduced in the initial implementation of RPK support in OpenSSL 3.2. The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-12797 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0316 <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in OpenSSL ausnutzen, um Sicherheitsvorkehrungen zu umgehen.</p> <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in OpenSSL ausnutzen, um Sicherheitsvorkehrungen zu umgehen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0316