Streaming AEAD does not authenticate stream structure

CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.

No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.

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.

Source published

9 Aug 2026 12:00:00 UTC

Source modified

12 Oct 2026 18:00:14 UTC

Observed here

24 Oct 2026 13:19:54 UTC

Source terms

OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.