2 advisory ignore entries no longer match anything (`quick-xml` already patched in `Cargo.lock`)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
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.lockis 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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/oxidizer
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
microsoft/oxidizer#738 · 52 comments ·
Maintainers usually reply within 1 day
All issues in microsoft/oxidizer
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
bytecodealliance/wrpc#1785 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
longbridge/nsh#2758 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
antithesishq/bombadil#473 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
libracoder/kiri#669 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
nowledge-co/hawdb#1881 ·
Maintainers usually reply within 1 day