Repository navigation
Bump rustix to 1.1.6 to clear RUSTSEC-2026-0486 - #155
Merged
Merged
Conversation
rustix 1.1.5's xattr functions mark unwritten bytes as initialized when given a zero-length buffer. rustix reaches this crate only as a dev-dependency through tempfile, and nothing here calls the xattr API, so the shipped binary was never affected. The lockfile still carried the vulnerable version, which the audit workflow flags. rustix 1.1.6 requires a newer bitflags, which moves from 2.6.0 to 2.13.2. Only rustix depends on bitflags, so it is also dev-only. Closes #154
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
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.
Resolves RUSTSEC-2026-0486. In
rustix1.1.5, the xattr functions mark unwritten bytes as initialized when they're given a zero-length buffer. This PR updates the lockfile torustix1.1.6, which fixes it.Impact
rustixreaches this crate only as a dev-dependency, throughtempfile. Nothing here calls the xattr API, so the shipped binary and the published crate were never affected.cargo tree -e normal --target all -i rustixcomes back empty. The lockfile still carried the vulnerable version, and that's what the audit workflow flags.rustix1.1.6 needs a newerbitflags, sobitflagsmoves from 2.6.0 to 2.13.2.rustixis the only crate that depends onbitflags, so it's dev-only too.Verification
cargo auditreports RUSTSEC-2026-0486 againstmain'sCargo.lockand reports nothing on this branch.cargo fmt --check,RUSTFLAGS=-Dwarnings cargo clippy --all-targets --all-featuresandcargo testall pass.No version bump, so merging this doesn't cut a release. Downstream users don't need one, because the change only touches dev-dependencies.
Closes #154