{"answers":{"affected":"1 open source package ship an affected version, including quinn-proto.","exploited":"There is no known exploitation of RUSTSEC-2026-0339 in the wild and no public exploit code.","fix":"Upgrade quinn-proto to 0.11.17 or later.","what":"RUSTSEC-2026-0339 is a denial of service vulnerability in quinn-proto, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0339 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0339 is a denial of service vulnerability in quinn-proto, published on 17 Aug 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 RUSTSEC-2026-0339 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- quinn-proto (crates.io): affected from 0.6.0; 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/RUSTSEC-2026-0339/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0339/index.md)","id":"RUSTSEC-2026-0339","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0339/index.md","name":"RUSTSEC-2026-0339","record":{"aliases":["GHSA-hmxj-32vh-65vr"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"QUIC protocol library","requires_auth":"none","summary":"A remote attacker can cause unbounded memory growth in quinn-proto by flooding NEW_CONNECTION_ID frames, leading to denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"When processing a NEW_CONNECTION_ID frame, quinn-proto queues a RETIRE_CONNECTION_ID frame for\neach connection ID that the peer asked it to retire. The normal path bounds this queue and closes\nthe connection with a CONNECTION_ID_LIMIT_ERROR if the bound would be exceeded. However, the path\nhandling a connection ID that had already been retired pushed onto the queue without applying\nthe limit and without deduplicating.\n\nA peer that has completed the handshake can first send a NEW_CONNECTION_ID frame with a large\n`retire_prior_to` value to advance the receiver's connection ID window, and then repeatedly send\nNEW_CONNECTION_ID frames with sequence numbers below that window. Each such frame adds another\nentry to the queue. The queue is only drained by sending RETIRE_CONNECTION_ID frames, which are\nsubject to congestion control, so a peer that withholds acknowledgements can stall the drain while\ncontinuing to flood, growing the victim's memory use without bound.\n\nThe flaw was corrected in 0.11.17 by applying the same limit on the already-retired path.\n\nThanks to [@scadastrangelove](https://github.com/scadastrangelove) for reporting this issue.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Unbounded growth of pending connection ID retirements in quinn-proto","id":"RUSTSEC-2026-0339","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.11.17"],"introduced":["0.6.0"],"last_affected":[],"package":"quinn-proto","purl":"pkg:cargo/quinn-proto","source":"RUSTSEC-2026-0339"}],"products":null,"published":"2026-08-17","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A remote attacker can cause unbounded memory growth in quinn-proto by flooding NEW_CONNECTION_ID frames, leading to denial of service.","url":"https://insights.sbomify.com/RUSTSEC-2026-0339/"}