Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5

Peer minimum ACK delay can panic quinn-proto when ACK_FREQUENCY transmission is enabled

GHSA-3g6h-r5qx-f6hq

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (quinn-proto 0.11.18), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • crates.io quinn-proto

    Affected
    >= 0.11.0, < 0.11.18
    Fixed in
    0.11.18

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

When sending ACK_FREQUENCY frames is enabled through `TransportConfig::ack_frequency_config(Some(..))`, the peer's transport parameters could cause `AckFrequencyState::candidate_max_ack_delay` to call `Duration::clamp` with a minimum greater than its maximum, which panics. For example, a peer advertising a `min_ack_delay` of 100,000 microseconds and a `max_ack_delay` of 100 milliseconds passes transport parameter validation. At a 5 ms RTT, the lower bound of the clamp becomes 100 ms while the upper bound is 25 ms, violating the precondition of `clamp` and panicking while driving the connection. Both automatically derived and explicitly configured maximum ACK delays use this calculation. Sending ACK_FREQUENCY frames is disabled by default, so only endpoints that opt in are affected. The flaw was corrected in 0.11.18 by computing the delay with explicit minimum and maximum bounds instead of `clamp`. Thanks to @zerox80 for reporting this issue.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record RUSTSEC-2026-0340

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-3g6h-r5qx-f6hq

Advisory: Peer minimum ACK delay can panic quinn-proto when ACK_FREQUENCY transmission is enabled
IDs: GHSA-3g6h-r5qx-f6hq
Record: https://patchnext.com/advisories/rustsec-2026-0340 (revision 1, source checked 23 Oct 2026, 22:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: quinn-proto 0.11.18. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io quinn-proto: affected >= 0.11.0, < 0.11.18; fixed in 0.11.18

## Suggested inspection (read-only)
- crates.io quinn-proto: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on quinn-proto.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/RUSTSEC-2026-0340 (OSV record RUSTSEC-2026-0340 lists affected ranges: crates.io quinn-proto >=0.11.0 <0.11.18 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…