🛡️ RUSTSEC-2026-0239 — dcrypt-symmetric
Description
Streaming AEAD does not authenticate stream structure
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.
Affected software
RUSTSEC-2026-0239 is recorded against 1 package.
- dcrypt-symmetric
Timeline and source
Published on 9 August 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
crates.io (Package)
rustsec.org (Advisory)
github.com (Advisory)
github.com (Web)
github.com (Web)
Details
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| dcrypt-symmetric | — | — |
References
More RUSTSEC 2026 advisories
Browse all of RUSTSEC 2026 in the advisory index.
Free Vulnerability Check
Is your site affected by RUSTSEC-2026-0239?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against RUSTSEC-2026-0239 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.