Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Remote peer can panic quinn-proto with zero-length STREAM frames during unordered reads

GHSA-465w-v9q3-7j98

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.7.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
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

When a stream is read in unordered mode (for example through `RecvStream::read(false)` in quinn-proto or `read_unordered` in `quinn`), quinn-proto proactively deduplicates received data by recording received ranges in a `RangeSet` through its `replace` method. When an incoming STREAM frame carried an empty payload, the `Drop` implementation of the iterator returned by `replace` inserted an empty range into the set, violating the invariant that stored ranges are non-empty. Subsequent frames overlapping that region then caused a panic while processing the stream. A remote peer can trigger this with five small STREAM frames (two of them zero-length) once the application has put the stream in unordered-read mode. The default ordered read path is not affected. The flaw was corrected in 0.11.18 by ignoring empty ranges in `RangeSet::replace`. Thanks to Otto Hermann (@ojhermann) 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-0338

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-465w-v9q3-7j98

Advisory: Remote peer can panic quinn-proto with zero-length STREAM frames during unordered reads
IDs: GHSA-465w-v9q3-7j98
Record: https://patchnext.com/advisories/rustsec-2026-0338 (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: Unrated
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.7.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-0338 (OSV record RUSTSEC-2026-0338 lists affected ranges: crates.io quinn-proto >=0.7.0 <0.11.18 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…