docs(security): triage RUSTSEC-2026-0190 (anyhow < 1.0.103 downcast_mut unsoundness)#27
Merged
Merged
Conversation
…ness) anyhow 1.0.102 flagged by cargo audit. It is a phantom transitive dep reachable only via the wasm32-wasip3 chain (getrandom 0.4.2 -> wasip3 -> wit-bindgen -> anyhow); cargo tree cannot reach it on any real target, so the unsound Error::downcast_mut path is unreachable in rustEZ builds. Cargo.lock is gitignored here, so nothing is pinned and CI's fresh resolve now picks the patched anyhow 1.0.103 automatically. Local `cargo update -p anyhow --precise 1.0.103` refreshes dev/audit runs to match. Records the triage + fix rationale. Refs #26. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CALA6Gum4MdPTeEPf6vant
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #26.
Summary
cargo auditflagged RUSTSEC-2026-0190 — unsoundness inanyhow::Error::downcast_mut()(safe-code-triggerable Stacked-Borrows violation; affected< 1.0.103, patched1.0.103). Our local lock hadanyhow 1.0.102.Triage
anyhowis not a direct dep of any workspace crate. It enters only via a target-gated wasm chain —getrandom 0.4.2 → wasip3 → wit-bindgen → … → anyhow— that resolves solely forwasm32-wasip3.cargo tree -i anyhow(even--target all) reports "nothing to print" on real hosts. rustEZ is a tokio Junos automation library, never built for wasm, so the unsound path is unreachable in practice.Fix
Cargo.lockis gitignored in this repo, so nothing is pinned and there's no tracked lockfile to change. CI regenerates the lock on each run and now auto-resolves the patchedanyhow 1.0.103. Localcargo update -p anyhow --precise 1.0.103refreshes dev/audit runs to match. No crate version bump, no republish (library ignores lock downstream; rustez-cli unpublished).This PR commits the triage/analysis dump only.
Verification
cargo audit→ RUSTSEC-2026-0190 occurrences: 0 (only residual is the pre-existing allowed yanked-aes 0.9.0warning)cargo check --workspaceclean ·cargo test -p rustez→ 52 passed🤖 Generated with Claude Code
https://claude.ai/code/session_01CALA6Gum4MdPTeEPf6vant