{"answers":{"affected":"1 open source package ship an affected version, including dcrypt-symmetric.","exploited":"There is no known exploitation of RUSTSEC-2026-0239 in the wild and no public exploit code.","fix":"Upgrade dcrypt-symmetric to 2.0.0 or later.","what":"RUSTSEC-2026-0239 is a vulnerability in dcrypt-symmetric, published on 9 Aug 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0239 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0239 is a vulnerability in dcrypt-symmetric, published on 9 Aug 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0239 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- dcrypt-symmetric (crates.io): affected from 0.0.0-0; fixed in 2.0.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/RUSTSEC-2026-0239/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0239/index.md)","id":"RUSTSEC-2026-0239","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0239/index.md","name":"RUSTSEC-2026-0239","record":{"aliases":["GHSA-8cwp-4826-jg9f"],"analysis":null,"analysis_generated_by":null,"assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In all published versions of `dcrypt-symmetric` before 2.0.0, version-1 GCM and\nChaCha20-Poly1305 streams used unauthenticated terminator, counter, and length\nfields. Decryptors trusted transmitted counters, allocated from unbounded\nlengths, and discarded plaintext that did not fit a caller's single read\nbuffer. An attacker could obtain successful truncated EOF, omit, replay, or\nreorder frames within a stream, or request an allocation approaching 4 GiB.\n\nVersion 2.0.0 introduces the `DCRSTRM2` format, which authenticates its version,\nalgorithm, random stream identifier, base nonce, strict sequence, bounded\nlengths, final flag, and caller AAD. It enforces authenticated finality and\nphysical EOF, bounds frames to 16 KiB before allocation, retains partial-read\nplaintext, and rejects legacy version-1 input. Existing version-1 ciphertext\ncannot retrospectively prove completeness or ordering and must be migrated only\nthrough an application-specific, explicitly trusted process.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Streaming AEAD does not authenticate stream structure","id":"RUSTSEC-2026-0239","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":null,"year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["2.0.0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"dcrypt-symmetric","purl":"pkg:cargo/dcrypt-symmetric","source":"RUSTSEC-2026-0239"}],"products":null,"published":"2026-08-09","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":null,"url":"https://insights.sbomify.com/RUSTSEC-2026-0239/"}