Skip to content

Remove the ruzstd advisory ignore: Cargo.lock is on ruzstd 0.9.1 - #62

Open
zyl71 wants to merge 1 commit into
ngodzik:mainfrom
zyl71:remove-stale-advisory-ignores
Open

zyl71 wants to merge 1 commit into
ngodzik:mainfrom
zyl71:remove-stale-advisory-ignores

Conversation

@zyl71

@zyl71 zyl71 commented Nov 20, 2026 •

Copy link
Copy Markdown

Closes #61

deny.toml still ignores the advisory below, but Cargo.lock on main already holds a patched version of the crate, so the entry no longer suppresses anything. This pull request removes it, together with the comments that explained it.

Advisory Summary In Cargo.lock now Patched in Severity
RUSTSEC-2026-0344 Decompression bomb in ruzstd: a tiny input can exhaust memory (OOM) ruzstd 0.9.1 0.9.1 high

Why remove it. 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-deny would stay silent about it.

What was checked, and what was not.

  • Read from main at commit 334ad3fec0ca on 2026-11-20: the id is on an active line of the config, and no version of the affected crate in Cargo.lock is inside the affected range of its advisory (RustSec records).
  • The change touches only deny.toml. No Rust source and no lock file is changed. The edited file parses as TOML, and every other ignore entry and setting is unchanged.
  • We did not run cargo deny check advisories locally, because we do not build or execute anything from this repository. CI is the first run of the tool on this change.

Not part of this change, but possibly useful: cargo-deny reports such entries as advisory-not-detected warnings, and unused-ignored-advisory = "deny" under [advisories] turns them into errors.

Disclosure: the check, the edit and this text were produced with automated tooling, including an LLM.

Feel free to close this if it is not useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Ignore entry for RUSTSEC-2026-0344 no longer matches anything (ruzstd is already at 0.9.1)

1 participant