CVE-2026-124709: OpenSSL · Memory Leak
Affects OpenSSLSource CVE Database V5
Not known to be exploited · fixed in 4.1.1 : update OpenSSL when convenient.
Data as of 17 Nov 2026, 08:35 UTC
Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 4.1.1, 4.0.4, 3.5.10
Exploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade OpenSSL to 4.1.1, 4.0.4 or 3.5.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenSSLOpenSSL | Affected
| Fixed in
|
| OpenSSLOpenSSL | Affected
| Fixed in
|
| OpenSSLOpenSSL | Affected
| Fixed in
|
AI-suggested
Fixed versions of OpenSSL are 3.5.10, 4.0.4, and 4.1.1. Users should upgrade to these versions or later to remediate this issue. No other mitigation or workaround is indicated by the vendor advisory.
Description
CVE-2026-124709 is a memory management vulnerability in OpenSSL's QUIC server implementation. When a QUIC server rejects a stream and the peer resets it before the rejection is signaled, the server retains the stream's state indefinitely, causing memory growth. This can lead to a denial of service by exhausting server memory. The issue affects OpenSSL versions 3.5.0 through 3.5.9, 4.0.0 through 4.0.3, and 4.1.0. Fixed versions are 3.5.10, 4.0.4, and 4.1.1.
References
- openssl-library.org/news/secadv/20261117.txt (opens in a new tab)
- github.com/openssl/openssl/commit/ead311df1037e7994a6d86c7e862d71ad59c52c7 (opens in a new tab)
- github.com/openssl/openssl/commit/22291a6af12f158fbb13bfbd572a33dbdbf290d2 (opens in a new tab)
- github.com/openssl/openssl/commit/f3acb0a3328046741479482c51cec815839e1b05 (opens in a new tab)