Skip to main content
CVE-2026-124709VulnerabilityPublished

openssl · Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime

Affects opensslSource GCVE Database

0
Compare
Authoritative record:CVE-2026-124709· Low

Not known to be exploited : upgrade to 3.1.7 when convenient.

Data as of 17 Nov 2026, 11:04 UTC

Severity
Low

Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Affects
QUIC servers prior to 3.1.7
Patch
Available – fixed in 3.1.7

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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/openssl to 3.1.7.

Affected software

ProductAffectedFixed in
GitHubopenssl/opensslpkg:github/openssl/opensslOther threatsAffected
  • <3.1.7
Fixed in
  • 3.1.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to OpenSSL version 3.1.7 or later, where this issue is fixed. No additional mitigation is required as the fix addresses the memory retention problem.

Description

A vulnerability in QUIC servers prior to version 3.1.7 allows a remote client to cause unbounded memory growth by repeatedly opening and resetting streams. This occurs because the server retains the state of rejected streams if the peer resets the stream before the rejection is signaled, leading to a denial of service due to memory exhaustion. The issue does not cause memory corruption or data disclosure and requires a long-lived connection for exploitation.

References

Community reviews

Loading reviews…