fix(deps): bump nostr to 0.44.6 to clear RUSTSEC-2026-0216 - #10733
Merged
Conversation
nostr 0.44.4 has a reachable panic in the NIP-44 v2 decrypt path and was yanked; async-utility 0.3.1 was yanked as well. Both fail Cargo Deny. Lockfile only - the 0.44 requirement in crates/goose/Cargo.toml is unchanged.
Abhijay007
approved these changes
Jul 27, 2026
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
2 participants
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.
Cargo Deny has been failing on
mainsince the 07-26 nightly, and on every open PR. Three errors, all in thenostrtree:RUSTSEC-2026-0216- reachable panic / remote DoS innostr0.44.4's NIP-44 v2 decrypt pathnostr0.44.4async-utility0.3.1Lockfile only; the
nostr = "0.44"requirement incrates/goose/Cargo.tomlis unchanged.Verified with
cargo metadata --locked(no re-resolution needed) andcargo check -p goose --features nostr,rustls-tls --locked.Note: a plain
cargo updatealso re-picks ~15 unrelatedwindows-sys/base64/getrandomedges downward, because those crates declare open ranges (e.g.windows-sys >=0.60.2, <0.62) and cargo resolves ranges to the low end. That churn is latent in the lockfile and unrelated to this advisory, so it is left out here rather than mixed into a security fix that touches Windows build edges.