CVE-2026-102820
pageant provides a [PageantStream] type that implements [AsyncRead] …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/Eugeny/russh/commit/5d566989ebabfdebfe6b33243d31765a0812260b
- github.com/Eugeny/russh/releases/tag/v0.63.2
- github.com/Eugeny/russh/security/advisories/GHSA-g4mp-vgx3-xrvm
- nvd.nist.gov/vuln/detail/CVE-2026-102820
- github.com/advisories/GHSA-g4mp-vgx3-xrvm
- nvd.nist.gov/vuln/detail/CVE-2026-102820
- cve.org/CVERecord?id=CVE-2026-102820
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.