Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Streaming AEAD does not authenticate stream structure

GHSA-8cwp-4826-jg9f

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (dcrypt-symmetric 2.0.0), 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

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.

In all published versions of `dcrypt-symmetric` before 2.0.0, version-1 GCM and ChaCha20-Poly1305 streams used unauthenticated terminator, counter, and length fields. Decryptors trusted transmitted counters, allocated from unbounded lengths, and discarded plaintext that did not fit a caller's single read buffer. An attacker could obtain successful truncated EOF, omit, replay, or reorder frames within a stream, or request an allocation approaching 4 GiB. Version 2.0.0 introduces the `DCRSTRM2` format, which authenticates its version, algorithm, random stream identifier, base nonce, strict sequence, bounded lengths, final flag, and caller AAD. It enforces authenticated finality and physical EOF, bounds frames to 16 KiB before allocation, retains partial-read plaintext, and rejects legacy version-1 input. Existing version-1 ciphertext cannot retrospectively prove completeness or ordering and must be migrated only through an application-specific, explicitly trusted process.

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-0239

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-8cwp-4826-jg9f

Advisory: Streaming AEAD does not authenticate stream structure
IDs: GHSA-8cwp-4826-jg9f
Record: https://patchnext.com/advisories/rustsec-2026-0239 (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: dcrypt-symmetric 2.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io dcrypt-symmetric: affected >= 0.0.0-0, < 2.0.0; fixed in 2.0.0

## Suggested inspection (read-only)
- crates.io dcrypt-symmetric: 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 dcrypt-symmetric.
- 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-0239 (OSV record RUSTSEC-2026-0239 lists affected ranges: crates.io dcrypt-symmetric >=0.0.0-0 <2.0.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…