{"answers":{"affected":"1 open source package ship an affected version, including quinn-proto.","exploited":"There is no known exploitation of RUSTSEC-2026-0340 in the wild and no public exploit code.","fix":"Upgrade quinn-proto to 0.11.18 or later.","what":"RUSTSEC-2026-0340 is a denial of service vulnerability in quinn-proto, published on 14 Sep 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-0340 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0340 is a denial of service vulnerability in quinn-proto, published on 14 Sep 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-0340 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- quinn-proto (crates.io): affected from 0.11.0; fixed in 0.11.18\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-0340/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0340/index.md)","id":"RUSTSEC-2026-0340","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0340/index.md","name":"RUSTSEC-2026-0340","record":{"aliases":["GHSA-3g6h-r5qx-f6hq"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Rust QUIC library","requires_auth":"none","summary":"A remote attacker can cause a denial of service by sending crafted transport parameters to a quinn-proto server with ACK frequency enabled.","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 sending ACK_FREQUENCY frames is enabled through\n`TransportConfig::ack_frequency_config(Some(..))`, the peer's transport parameters could cause\n`AckFrequencyState::candidate_max_ack_delay` to call `Duration::clamp` with a minimum greater\nthan its maximum, which panics.\n\nFor example, a peer advertising a `min_ack_delay` of 100,000 microseconds and a `max_ack_delay`\nof 100 milliseconds passes transport parameter validation. At a 5 ms RTT, the lower bound of the\nclamp becomes 100 ms while the upper bound is 25 ms, violating the precondition of `clamp` and\npanicking while driving the connection. Both automatically derived and explicitly configured\nmaximum ACK delays use this calculation.\n\nSending ACK_FREQUENCY frames is disabled by default, so only endpoints that opt in are affected.\n\nThe flaw was corrected in 0.11.18 by computing the delay with explicit minimum and maximum bounds\ninstead of `clamp`.\n\nThanks to [@zerox80](https://github.com/zerox80) 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":"Peer minimum ACK delay can panic quinn-proto when ACK_FREQUENCY transmission is enabled","id":"RUSTSEC-2026-0340","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.18"],"introduced":["0.11.0"],"last_affected":[],"package":"quinn-proto","purl":"pkg:cargo/quinn-proto","source":"RUSTSEC-2026-0340"}],"products":null,"published":"2026-09-14","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 a denial of service by sending crafted transport parameters to a quinn-proto server with ACK frequency enabled.","url":"https://insights.sbomify.com/RUSTSEC-2026-0340/"}