{"answers":{"affected":"4 open source packages ship an affected version, including quinn-proto.","exploited":"There is no known exploitation of CVE-2026-25800 in the wild and no public exploit code.","fix":"Upgrade quinn-proto to a fixed version for your release line: 0.11.15 or 0.11.17.","what":"CVE-2026-25800 is a high-severity denial of service vulnerability in quinn-rs quinn, published on 23 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-25800 and fix it if it is affected.\n\nWhat it is: CVE-2026-25800 is a high-severity denial of service vulnerability in quinn-rs quinn, published on 23 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-25800 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- quinn-proto (crates.io): affected from 0.0.0-0; fixed in 0.11.15\n- quinn-proto (crates.io): affected from 0.1.0; fixed in 0.11.15\n- quinn-proto (crates.io): affected from 0.1.0; fixed in 0.11.15\n- quinn-proto (crates.io): affected from 0.11.15; fixed in 0.11.17\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-25800/ (Markdown: https://insights.sbomify.com/CVE-2026-25800/index.md)","id":"CVE-2026-25800","markdown":"https://insights.sbomify.com/CVE-2026-25800/index.md","name":"CVE-2026-25800","record":{"aliases":["DEBIAN-CVE-2026-25800","GHSA-4w2j-m93h-cj5j","GHSA-qfwj-vfxf-92j2","MINI-4jv8-9w8q-jqqc","MINI-4xpc-vv54-h77c","MINI-7534-x6x6-w9v6","MINI-7r8w-793h-pfj5","MINI-fcq4-rjvw-vgm5","MINI-fpwj-m5pm-f6vh","MINI-j9pc-627p-wh5q","MINI-px9r-6g8c-32f3","MINI-r38x-v7j7-8q99","MINI-r8wp-qphg-v6m7","MINI-vf4g-g954-w9wj","RUSTSEC-2026-0185","RUSTSEC-2026-0341","UBUNTU-CVE-2026-25800","openSUSE-SU-2026:11635-1","openSUSE-SU-2026:11662-1","openSUSE-SU-2026:21870-1"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust QUIC library","requires_auth":"none","summary":"Remote attackers can cause memory exhaustion in applications using the quinn-proto library by sending fragmented QUIC stream data with gaps.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"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.","ecosystems":["crates.io","openSUSE:Leap 16.0","openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"quinn-proto has remote memory exhaustion from unbounded out-of-order stream reassembly","id":"CVE-2026-25800","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":7,"n_references":3,"next":{"headline":"New API has Potential XSS in its MarkdownRenderer component","id":"CVE-2026-25802"},"packages":[{"ecosystem":"crates.io","fixed":["0.11.15"],"introduced":["0.0.0-0"],"last_affected":[],"package":"quinn-proto","purl":"pkg:cargo/quinn-proto","source":"RUSTSEC-2026-0185"},{"ecosystem":"crates.io","fixed":["0.11.15"],"introduced":["0.1.0"],"last_affected":[],"package":"quinn-proto","purl":null,"source":"GHSA-4w2j-m93h-cj5j"},{"ecosystem":"crates.io","fixed":["0.11.15"],"introduced":["0.1.0"],"last_affected":[],"package":"quinn-proto","purl":"pkg:cargo/quinn-proto","source":"GHSA-4w2j-m93h-cj5j"},{"ecosystem":"crates.io","fixed":["0.11.17"],"introduced":["0.11.15"],"last_affected":[],"package":"quinn-proto","purl":"pkg:cargo/quinn-proto","source":"RUSTSEC-2026-0341"},{"ecosystem":"openSUSE:Leap 16.0","fixed":["0.154.0-bp160.1.1"],"introduced":["0"],"last_affected":[],"package":"openai-codex","purl":"pkg:rpm/opensuse/openai-codex\u0026distro=openSUSE%20Leap%2016.0","source":"openSUSE-SU-2026:21870-1"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["0.152.0-1.1"],"introduced":["0"],"last_affected":[],"package":"openai-codex","purl":"pkg:rpm/opensuse/openai-codex\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2026:11662-1"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["0.12.7-1.1"],"introduced":["0"],"last_affected":[],"package":"python-uv","purl":"pkg:rpm/opensuse/python-uv\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2026:11635-1"}],"prev":{"headline":"ImageMagick has Division-by-Zero in YUV sampling factor validation, which leads to crash","id":"CVE-2026-25799"},"products":["quinn"],"published":"2026-07-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-23","vendors":["quinn-rs"]},"summary":"Remote attackers can cause memory exhaustion in applications using the quinn-proto library by sending fragmented QUIC stream data with gaps.","url":"https://insights.sbomify.com/CVE-2026-25800/"}