2 advisory ignore entries no longer match anything (`quick-xml` already patched in `Cargo.lock`)

Open Beginner friendly
#1,001 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
85/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
security

Research direction

Open .cargo/audit.toml and find the two active ignore lines for RUSTSEC-2026-0194 and RUSTSEC-2026-0195; delete just those entries and leave the remaining ignores untouched. First confirm in Cargo.lock that quick-xml is pinned at 0.41.0, the version that carries both fixes. Done means the file no longer names either advisory id and cargo audit runs without re-reporting them.

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-0194 Quadratic run time when checking a start tag for duplicate attribute names quick-xml 0.41.0 0.41.0 high
RUSTSEC-2026-0195 Unbounded namespace-declaration allocation in NsReader enables … quick-xml 0.41.0 0.41.0 high

What we checked on 2026-11-21, on the default branch at commit 2f5896e4d0f3, 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
193
Forks
32
Avg merge
2d 21m
Merged PRs (30d)
101

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 microsoft/oxidizer

All issues in microsoft/oxidizer

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.