fix(deps): bump bcrypt to 0.19.2 for RUSTSEC-2026-0199#416
Merged
Conversation
bcrypt 0.19.1 panics in `bcrypt::verify` / `HashParts::from_str` when given a 60-byte hash string containing a multi-byte UTF-8 character at certain byte positions (RUSTSEC-2026-0199). This is a denial-of-service if an attacker-controlled hash reaches those functions. The fix ships in bcrypt 0.19.2, which rejects non-ASCII hash bytes up front. The manifest already allows it (`bcrypt = "0.19"`), so this is a lockfile-only bump. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Summary
Bumps
bcryptfrom 0.19.1 to 0.19.2 (lockfile-only) to resolve RUSTSEC-2026-0199, which is failing thecargo-denySecurity check onmainand every open PR.The vulnerability
bcrypt::verify(password, hash)andHashParts::from_str(hash)panic instr::slice_error_failwhen given a 60-byte&strcontaining a multi-byte UTF-8 character at certain byte positions. The crate is#![forbid(unsafe_code)], so impact is limited to denial-of-service (no memory corruption) whenever an attacker-controlled hash string reaches those functions.Change
The manifest already declares
bcrypt = "0.19", so this is aCargo.lock-only update:This is repo-wide (not tied to any feature branch), so it is raised directly against
main. Once merged, other open PRs go green on the Security check after a rebase.🤖 Generated with Claude Code