3 advisory ignore entries no longer match anything (`zstd`, `zstd-safe` already patched in `Cargo.lock`)

Open Beginner friendly
#1,785 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
security

Research direction

Open .cargo/audit.toml and delete the three active ignore lines for RUSTSEC-2026-0391, RUSTSEC-2026-0398 and RUSTSEC-2026-0403. Confirm in Cargo.lock that zstd is 0.14.3 and zstd-safe is 8.2.0, all outside the affected ranges. Then run cargo audit on the branch: done means it reports no advisory for these crates now that the ignores are gone.

Written by the indexing model from the issue text.

Description

Hi, and thanks for maintaining this project.

.cargo/audit.toml still ignores the advisories below. Cargo.lock on the default branch already holds a patched version of the crate, so the entries no longer suppress anything and can be removed.

Advisory Summary In Cargo.lock now Patched in Severity
RUSTSEC-2026-0391 Data from an abandoned stream leaks into the next stream on a reused context zstd 0.14.3 0.13.4, 0.14.3 not scored
RUSTSEC-2026-0398 Seekable::decompress sets a Vec length beyond its capacity for offsets past … zstd-safe 8.2.0 7.4.0, 8.2.0 not scored
RUSTSEC-2026-0403 Uninitialized memory exposed when streaming decompression of a legacy frame … zstd-safe 8.2.0 7.4.0, 8.2.0 not scored

The fix for RUSTSEC-2026-0391 was backported to the previous release line (zstd 0.13.4); RustSec recorded this on 2026-11-02.

What we checked on 2026-11-21, on the default branch at commit 577e56a616cb, by reading public files only:

  • Each id is on an active (non-comment) line of the file.
  • For each advisory, no version of the affected crate in Cargo.lock is inside its affected range.

Why it is worth removing: an ignore entry keeps muting the advisory id for as long as it stays in the file. If the crate were later pinned back to an affected version, cargo-audit would stay silent about it.

Disclosure: the check and this text were produced with automated tooling, including an LLM. The repository files were re-read from the default branch on 2026-11-21.

Feel free to close this if it is not useful.

Dominant language
Rust
Stars
336
Forks
48
Avg merge
10h 39m
Merged PRs (30d)
203

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bytecodealliance/wrpc

All issues in bytecodealliance/wrpc

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.