QUIC STREAM Fragment Metadata DoS
Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.
- Published
- Sep 29, 2026
- Updated
- Oct 8, 2026
- EPSS
- 0.5% · 38th percentile
- CWE
- CWE-770
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| openssl | openssl | cpe:2.3:a:openssl:openssl |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- openssl openssl3.4.0 and later · before 3.4.8
- openssl openssl3.5.0 and later · before 3.5.9
- openssl openssl3.6.0 and later · before 3.6.5
- openssl openssl4.0.0 and later · before 4.0.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.
OpenSSL OpenSSL
- 4.0.0 and later · before 4.0.3affected · semver
- 3.6.0 and later · before 3.6.5affected · semver
- 3.5.0 and later · before 3.5.9affected · semver
- 3.4.0 and later · before 3.4.8affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | openssl | before 3.5.7-1~deb13u3 | 3.5.7-1~deb13u3 |
| Debian:14 | openssl | before 3.6.5-1 | 3.6.5-1 |
| Red Hat:hummingbird:1 | openssl | before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
| Red Hat:hummingbird:1 | openssl-config-fips | before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
| Red Hat:hummingbird:1 | openssl-devel | before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
| Red Hat:hummingbird:1 | openssl-devel-engine | before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
| Red Hat:hummingbird:1 | openssl-fips-provider-upstream | before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
| Red Hat:hummingbird:1 | openssl-libs | before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
| Red Hat:hummingbird:1 | openssl-perl | before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
| Red Hat:hummingbird:1 | openssl3 | before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
| Red Hat:hummingbird:1 | openssl3-devel | before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
| Red Hat:hummingbird:1 | openssl3-devel-engine | before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
| Red Hat:hummingbird:1 | openssl3-libs | before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
Same product
openssl: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remKEV90Now
- CVE-2021-3711SM2 Decryption Buffer Overflow65This week
- CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code 65This week
- CVE-2016-2108The ASN.1 implementation in OpenSSL before 1.0.1o and 1.0.2 before 1.0.2c allows remote attackers to execute arbitrary code or cause a denia62This week
- CVE-2016-6309statem/statem.c in OpenSSL 1.1.0a does not consider memory-block movement after a realloc call, which allows remote attackers to cause a den60This week
- CVE-2022-3786X.509 Email Address Variable Length Buffer Overflow58Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| OpenSSL OpenSSL | 3.4.8 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.5.9 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.6.5 | Vendor (CNA) |
| OpenSSL OpenSSL | 4.0.3 | Vendor (CNA) |
| azl3 cloud-hypervisor 52.0.152-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kata-containers 4.1.0.kata0-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 openssl 3.3.7-6 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 openvmm 0.1.0-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 rust 1.75.0-31 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 rust 1.96.1-2 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:openssl | 3.5.7-1~deb13u3 · Debian:13 | Package registry (OSV) |
| red hat:openssl | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-config-fips | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-devel | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-devel-engine | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-fips-provider-upstream | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-libs | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl-perl | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl3 | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl3-devel | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl3-devel-engine | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:openssl3-libs | 0:3.5.9-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayOct 10, 2026+11 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Zhen Yan (AntAISecurityLab)reporter
- Bhabani Sankar Dasreporter
- Alexandr Nedvedickyremediation developer
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-847840 days apartQUIC: Unbounded RETIRE_CONNECTION_ID Backlog30Monitor
- CVE-2026-6307535 days apartQUIC ACK-only Packet Retention Can Cause Memory Exhaustion30Monitor
- CVE-2026-1445647 days apartUnbounded Memory Growth in QUIC Server Incoming Channel Queue30Monitor
- CVE-2026-6307435 days apartCMP Indefinite Cache Growth of ExtraCerts23Monitor
- CVE-2026-351890 days apartExcessive Memory Allocation in Relative CRLDP Processing21Monitor
- CVE-2026-758040 days apartQUIC Connection-Level Flow Control is Not Enforced for Streams21Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1218 · Sep 30, 2026(OpenSSL Güvenlik Zafiyeti)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-770 · Allocation of Resources Without Limits or ThrottlingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- FloodingCAPEC-125likelihood: High · Medium
- Excessive AllocationCAPEC-130likelihood: Medium · Medium
- XML Ping of the DeathCAPEC-147likelihood: Low · Medium
- Exponential Data ExpansionCAPEC-197likelihood: High · Medium
- Serialized Data Parameter BlowupCAPEC-229likelihood: High · High
- Serialized Data with Nested PayloadsCAPEC-230likelihood: Medium · High
- Oversized Serialized Data PayloadsCAPEC-231likelihood: Medium · High
- HTTP DoSCAPEC-469Low
ATT&CK techniques
- Network Denial of Service:Direct Network FloodT1498.001
- Network Denial of Service:Reflection AmplificationT1498.002
- Endpoint Denial of ServiceT1499
- Endpoint Denial of Service: OS Exhaustion FloodT1499.001
- Endpoint Denial of Service:Service Exhaustion FloodT1499.002
- Endpoint Denial of Service:Application Exhaustion FloodT1499.003
Change log
- CVSS— → 7.5
- Severity— → high
- SSVC exploitation— → none
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- github.com/openssl/openssl/commit/1f643b8bc735487b500a1f68a7fb3a22d5e38e23
- github.com/openssl/openssl/commit/279e7ee1392af98785746788168749491c74bd53
- github.com/openssl/openssl/commit/3ea6213e050e938ecbbf8c4eff32bec2736780eb
- github.com/openssl/openssl/commit/7127fb10888b49711c63128a09e524c0d2d5d0b2
- openssl-library.org/news/secadv/20260929.txt
Vendor advisories and official records. Exploit/PoC links are deliberately left out.