Servers and applications
CVE-2024-4741
Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously freed in some situations Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only applications that directly call the SSL_free_buffers function are affected by this…
- Severity
- Critical 9.8
- Published
- 13 Nov 2024
- Last changed
- 9 Nov 2026
- Added to UpHeron
- 9 Nov 2026
- Fixed in
- 1.1.1y, 3.0.14, 3.1.6, 3.2.2
- Exploit chance
- 3.3% in the next 30 daysHigher than 88% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- Use after free (CWE-416)
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Read data · Change data · Take it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H- Sources
- NVD
Description
Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously freed in some situations
Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only applications that directly call the SSL_free_buffers function are affected by this issue. Applications that do not call this function are not vulnerable. Our investigations indicate that this function is rarely used by applications.
The SSL_free_buffers function is used to free the internal OpenSSL buffer used when processing an incoming record from the network. The call is only expected to succeed if the buffer is not currently in use. However, two scenarios have been identified where the buffer is freed even when still in use.
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-121481Calling EVP_EncodeBlock() with an input length close to INT_MAX may overflow the calculation of the encoded output size and write past the end of the caller-supplied output buffer.Critical 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