Repository navigation
fix(deps): bump pageant to 0.2.4 for its out-of-bounds read advisory - #359
Merged
Merged
Conversation
pmaxhogan
force-pushed
the
fix/pageant-oob
branch
from
October 15, 2026 00:09
e0eddf7 to
8e3d2d5
Compare
Contributor
Coverage
Gate: passed - no coverage regression (epsilon 0.1 pp). |
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.
russh 0.64.1 (#352) still left
pageant(russh's Windows SSH-agent client) at 0.2.1 in Cargo.lock. That version is affected by GHSA-g4mp-vgx3-xrvm, an out-of-bounds read inpageant. This is a lockfile-only bump to 0.2.4, the latest patch in the 0.2 line russh already allows.pageant only compiles on Windows, so the windows-latest CI jobs are the real check here.
Tracked in #358. README checked, no changes needed.