Quinn is a pure-Rust, async-compatible implementation of the IETF QUIC transport protocol. Starting in version 0.1.0 and prior to version 0.11.15, the Assembler component that assembles unordered stream fragments into consecutive chunks of the stream incurs some overhead for non-contiguous fragments. Readers that read from a RecvStream in order (through an AsyncRead impl for example) will be sensitive to peers that send fragments while leaving out early parts of the stream, and in particular, fragments with many gaps (because these cannot be defragmented). In such a scenario, the receiving connection suffers from high buffer overhead, enabling memory exhaustion. Version 0.11.15 fixes the issue.
CVE-2026-25800
HIGHPre-NVD 7.57.5
EchelonGraph scoreLOW confidence
This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: cna:github_m
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: —CVSS: 7.5Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(low)
- EG Risk
- 38(Track)EG Risk 38/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- —
- KEV
- Not listed
Published
July 23, 2026
Last Modified
July 23, 2026
Advisory Details (3)
Auto-updated Jul 23, 2026Patch available. Sources: github, github_pr.
generic
RUSTSEC-2026-0185: quinn-proto: Remote memory exhaustion in quinn-proto from unbounded out-of-order stream reassembly › RustSec Advisory Database
https://rustsec.org/advisories/RUSTSEC-2026-0185.htmlgithub_pr Patch Available
proto: yield error on too many gaps in assembler
Patch available: quinn-rs/quinn quinn-proto-0.11.15 (PR #2694 merged 2026-06-22)
https://github.com/quinn-rs/quinn/pull/2694github Patch Available
Remote memory exhaustion in quinn-proto from unbounded out-of-order stream reassembly · Advisory · quinn-rs/quinn · GitHub
https://github.com/quinn-rs/quinn/security/advisories/GHSA-4w2j-m93h-cj5jWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 19:22 UTCEG score recompute
- 2026-07-23 19:21 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-25800?
CVE-2026-25800 is a high vulnerability published on July 23, 2026. Quinn is a pure-Rust, async-compatible implementation of the IETF QUIC transport protocol. Starting in version 0.1.0 and prior to version 0.11.15, the Assembler component that assembles unordered stream fragments into consecutive chunks of the stream incurs some overhead for non-contiguous…
When was CVE-2026-25800 disclosed?
CVE-2026-25800 was first published in the National Vulnerability Database on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-25800?
CVE-2026-25800 has a CVSS v3 base score of 7.5 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-25800?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25800, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-25800
Is Your Infrastructure Affected by CVE-2026-25800?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.