Servers and applications
CVE-2024-12797
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'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…
- Severity
- High 7.4
- Published
- 11 Feb 2025
- Last changed
- 6 Nov 2026
- Added to UpHeron
- 7 Nov 2026
- Fixed in
- 3.2.4, 3.3.3, 3.4.1
- Exploit chance
- 1.8% in the next 30 daysHigher than 79% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- CWE-392
- Attack
- Over the network · Only under certain conditions · No login needed · No user action needed
- Attacker can
- Read data · Change data
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N- Sources
- NVD
Description
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'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'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…
Affected software
| Software | Affected versions |
|---|---|
OpenSSLServers and applications · cpe:a:openssl:openssl |
|
About OpenSSL
open-source implementation of the SSL and TLS protocols
- GitHub stars
- 31,449GitHub, 15 Nov 2026
- Forks
- 11,615GitHub, 15 Nov 2026
- Latest release
- openssl-4.1.0GitHub, 15 Nov 2026
- Released
- 23 Oct 2026GitHub
- Developer
- Richard LevitteWikidata
- License
- Apache Software License 2.0Wikidata
- Written in
- C, assembly language, PerlWikidata
- First released
- 1998Wikidata
- First published on GitHub
- 15 Jan 2013GitHub
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 4.1 | 4.1.0 | Until 23 Nov 2027 |
| 4.0 | 4.0.3 | Until 14 May 2027 |
| 3.6 | 3.6.5 | Ended 1 Nov 2026 |
| 3.5 (LTS)LTS | 3.5.9 | Until 8 Apr 2030 |
| 3.4 | 3.4.8 | Ended 22 Oct 2026 |
| 3.3 | 3.3.7 | Ended 9 Apr 2026 |
From endoflife.date.
Vulnerabilities in OpenSSL
- In our list
- 335
- Published in the last 12 months
- 76
- Critical, last 12 months
- 6
- High, last 12 months
- 40
- Known exploited
- 1
- CVE-2026-95690Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory.Medium 5.3 18 Nov 2026
- CVE-2026-84786A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records.High 7.5 18 Nov 2026
- CVE-2026-121482Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size.High 7.5 18 Nov 2026
- CVE-2026-121481Integer Overflow in EVP_EncodeBlock() with Very Large Input LengthsCritical 9.8 18 Nov 2026
- CVE-2026-107494The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames.Critical 9.1 18 Nov 2026
- CVE-2026-35190Out-of-Bounds Read in TLS 1.3 Key-Share Processing with Suite B Certificate FlagMedium 5.3 17 Nov 2026