Skip to content

build(deps): bump pageant from 0.2.4 to 0.2.5 - #287

Merged
blaipr merged 1 commit into
mainfrom
fix/pageant-advisory
Nov 15, 2026
Merged

blaipr merged 1 commit into
mainfrom
fix/pageant-advisory

Conversation

@blaipr

@blaipr blaipr commented Nov 14, 2026

Copy link
Copy Markdown
Member

Problem

Dependabot alert #14: pageant 0.2.0–0.2.4 buffers frames of any size from a peer-controlled 4-byte length prefix, a memory-exhaustion DoS (GHSA-662x-8wvj-2276, CVE-2026-116775). Fixed in 0.2.5.

Change

cargo update -p pageant --precise 0.2.5. pageant is a Windows-only dependency of russh (the PuTTY agent client): the Linux binary and the published image never included it, so this changes nothing users run, hence build: rather than fix:.

The lockfile moves a few more lines: pageant 0.2.5 depends on windows-sys 0.52, and errno, rustix, tempfile and quinn-udp declare a range of windows-sys versions, so Cargo now resolves them to that one copy. tempfile's getrandom moves the same way, within its declared range (0.4.3 → 0.3.4). All of these are Windows-only except getrandom.

Compatibility

None.

Checklist

  • cargo test passes locally; cargo audit reports no vulnerabilities
  • The title reads as a CHANGELOG line for users (hidden: build)

Fixes GHSA-662x-8wvj-2276 (CVE-2026-116775): unbounded frame buffering on
a peer-controlled length prefix. pageant is a Windows-only dependency of
russh, so the Linux binary and the published image never included it.
@blaipr
blaipr merged commit e2da1f0 into main Nov 15, 2026
5 checks passed
@blaipr
blaipr deleted the fix/pageant-advisory branch November 15, 2026 00:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant