p PatchFirst

CVE-2026-102820

CVE-2026-102820 · pageant: Out-of-bounds read / oversized allocation in `pageant` MemoryMap::read via a malicious Pageant agent (Windows)

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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 6.2 · Medium · EPSS 0.2% · Fix available

Published
Updated

Stack: system

Affected products and versions

  • russh

    Versions
    • < 0.63.2: Affected

    No fix published

  • pageant

    Versions
    • < 0.2.3: Affected

    No fix published

  • rust-russh Debian:14

    Versions
    • 0.57.1-1
    • 0.57.1-2
    Affected ranges
    • ECOSYSTEM: < 0.64.1-1

    Update to 0.64.1-1

  • rust-russh Ubuntu:26.10

    Versions
    • 0.57.1-2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →