Skip to main content
Menu
CVEs

OpenSSL denial of service via unbounded QUIC frame queue

CVE-2026-107494EUVD-2026-128601GHSA-9X26-7724-X23JPublished November 18, 2026, updated

7.5HighCISA-ADP
Exploited
No known exploitation
Fix
Fixed in 4.1.1, 4.0.4, 3.5.10
Who is exposed
Not reported

Summary

OpenSSL's QUIC stack has a flaw where it queues a RETIRE_CONNECTION_ID frame for retransmitted NEW_CONNECTION_ID frames as well. A remote malicious QUIC peer could use this to queue an unlimited number of those frames.

Written by a model

Original description

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.

What to do

Upgrade to a fixed version: 4.1.1, 4.0.4, 3.5.10.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-107494 (Unbounded QUIC RETIRE_CONNECTION_ID Frame Sending Queue), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-107494 (entry last updated 2026-11-20):
Affected:
- OpenSSL OpenSSL: from 4.1.0, fixed in 4.1.1; from 4.0.0, fixed in 4.0.4; from 3.5.0, fixed in 3.5.10
Fixed versions: 4.1.1, 4.0.4, 3.5.10.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-107494 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-107494 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/openssl/openssl/pull/33544
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-107494
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-107494"}.

Affected versions

cve.now Index

48of 100 · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach20/20Affects OpenSSL (software on nearly every server, desktop or phone)
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 93 if added to CISA KEV
  • Would score about 88 if CISA's SSVC rates exploitation active
  • Would score about 53 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now1 day
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Posted on X by cve.now1 day
  5. Record last updated

Public exploit activity

100%0Posted on X by cve.nowNov 18Nov 22
  • EPSS: 0.39%
  • Posted on X by cve.now Nov 19

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Evidence 3

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-107494
RecordNVD · CVE-2026-107494
Other links 1
PatchGitHub · openssl/openssl · Pull request #33544

Questions about CVE-2026-107494

Is CVE-2026-107494 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-107494?

OpenSSL: from 4.1.0 before 4.1.1; from 4.0.0 before 4.0.4; from 3.5.0 before 3.5.10.

Source: cve.now feed data

How do I fix CVE-2026-107494?

Upgrade to a fixed version: 4.1.1, 4.0.4, 3.5.10.

Source: cve.now feed data

Why is it rated 7.5 High?

CVSS 7.5 scores the worst case. openssl rates it Low.

No corrections so far. Something wrong on this page? Report an error.