Skip to main content
No exploitation reportedFix available

CVE-2026-25800

No exploitation reported by the sources we read.

  • Published2026-07-23
  • Fixed in0.11.15
  • WeaknessCWE-770

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2026-07-2320:17CVE publishedNVD

Versions per branch

OSV
quinn-proto
BranchAffectedFixed in
0.x≥ 0.0.0-0, < 0.11.150.11.15
0.x≥ 0.1.0, < 0.11.150.11.15

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • quinn-rs quinn
    Affected
    • = >= 0.1.0, < 0.11.15no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-07-23

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • openai-codexopenSUSE:Tumbleweedall versions · fixed in 0.152.0-1.1
  • openai-codexopenSUSE:Leap 16.0all versions · fixed in 0.154.0-bp160.1.1
  • python-uvopenSUSE:Tumbleweedall versions · fixed in 0.12.7-1.1
  • rust-quinn-protoUbuntu:26.10all versions · no fixed version listed
  • rust-quinn-protoUbuntu:26.04:LTSall versions · no fixed version listed
  • rust-quinn-protoUbuntu:24.04:LTSall versions · no fixed version listed
  • rust-quinn-protoDebian:14all versions · fixed in 0.11.16-1
  • rust-quinn-protoDebian:13all versions · no fixed version listed

1 more package range on OSV.dev

Vendor advisories

  • CVE-2026-25800 Red Hat Product Security

    quinn: Quinn: Remote memory exhaustion via malformed QUIC stream fragments

Full record on NVD

Fix

  1. Update quinn-proto to 0.11.15

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2026-07-23
Last Modified
2026-10-24
NVD status
Deferred
GitHub Advisory
GHSA-4w2j-m93h-cj5j

Frequently asked questions

What is CVE-2026-25800?

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.

Is CVE-2026-25800 actively exploited?

Active exploitation of CVE-2026-25800 has not been confirmed. Its EPSS score was 0.8% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-25800?

CVE-2026-25800 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running quinn? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record