RUSTSEC-2026-0239

Source
https://rustsec.org/advisories/RUSTSEC-2026-0239
Import Source
https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2026-0239.json
JSON Data
https://api.test.osv.dev/v1/vulns/RUSTSEC-2026-0239
Aliases
  • GHSA-8cwp-4826-jg9f
Published
2026-08-09T12:00:00Z
Modified
2026-08-09T12:45:02.668544329Z
Summary
Streaming AEAD does not authenticate stream structure
Details

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.

Database specific
{
    "license": "CC0-1.0"
}
References

Affected packages

crates.io / dcrypt-symmetric

Package

Name
dcrypt-symmetric
View open source insights on deps.dev
Purl
pkg:cargo/dcrypt-symmetric

Affected ranges

Type
SEMVER
Events
Introduced
0.0.0-0
Fixed
2.0.0

Ecosystem specific

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

Database specific

categories
[
    "crypto-failure",
    "denial-of-service"
]
informational
null
cvss
null
source
"https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2026-0239.json"