RUSTSEC-2026-0340

See a problem?
Please try reporting it to the source first.

Source

https://rustsec.org/advisories/RUSTSEC-2026-0340

Import Source

https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2026-0340.json

JSON Data

https://api.osv.dev/v1/vulns/RUSTSEC-2026-0340

Aliases

GHSA-3g6h-r5qx-f6hq

Published

2026-09-14T12:00:00Z

Modified

2026-10-12T18:15:01Z

Severity

7.5 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CVSS Calculator

Summary

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

Details

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.

Database specific

{
    "license":  "CC0-1.0"
}

References

Affected packages

crates.io / quinn-proto

Package

Name: quinn-proto; View open source insights on deps.dev
Purl: pkg:cargo/quinn-proto

Affected ranges

Type: SEMVER
Events: Introduced

0.11.0

Fixed

0.11.18

Ecosystem specific

{
    "affected_functions":  null,
    "affects":  {
        "arch":  [],
        "functions":  [],
        "os":  []
    }
}