CVE-2026-102820

pageant provides a [PageantStream] type that implements [AsyncRead] and [AsyncWrite] traits and can be used to talk to a running Pageant instance. Prior to pageant 0.2.3, the Windows pageant crate's pageant/src/wmmessage.rs MemoryMap::read function trusts a peer-controlled u32 response length supplied through the 8192-byte Pageant shared-memory mapping reached by AgentClient::connect_pageant. A local process that impersonates the Pageant window can make query_pageant_direct allocate up to approximately 4 GiB and copy beyond the mapped view, reliably crashing a russh client and conditionally exposing adjacent committed memory. This issue is fixed in pageant 0.2.3.

CVSS 3.1

6.2CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

0.2% chance of exploitation in the next 30 days; higher than 8% of CVEs (scores of 2026-10-25)

CWEs

CWE-125, CWE-789

Published

2026-09-29

Modified

2026-09-30

Record from

the NVD, synced 2026-10-19

Packages (OSV)

References

• https://github.com/Eugeny/russh/commit/5d566989ebabfdebfe6b33243d31765a0812260b
• https://github.com/Eugeny/russh/releases/tag/v0.63.2
• https://github.com/Eugeny/russh/security/advisories/GHSA-g4mp-vgx3-xrvm
• https://github.com/Eugeny/russh/security/advisories/GHSA-g4mp-vgx3-xrvm

Check your stackJSON