CVE Tools

CVE-2026-107494

Unbounded QUIC RETIRE_CONNECTION_ID Frame Sending Queue

No known exploitation. EPSS puts it in the 3rd percentile. Fixed versions are out.

Check it yourself

No ready-made check. Neither Nuclei nor OpenVAS has one for this CVE yet.

Request a scan

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • OpenSSLAffected: ≥ 4.1.0, < 4.1.1Upgrade to: 4.1.1Affected: ≥ 4.0.0, < 4.0.4Upgrade to: 4.0.4Affected: ≥ 3.5.0, < 3.5.10Upgrade to: 3.5.10Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

Issue summary: The 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. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS3rd
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.1% chance of exploitation activity in the next 30 days, which ranks it in the 3rd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

7 events over 2 days, from the signal feeds we watch.

  1. Record updatedrecord updated
  2. Record updated
  3. Publishedweakness classified, att&ck mapped, record updated

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Scored 7.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity NoneNo integrity impact
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for OpenSSL, not every advisory.