2.3
LowCVSS 4.0 · from GitHub_M
CVE-2026-116775
pageant: unbounded frame buffering on peer-controlled 4-byte length prefix (memory-exhaustion DoS)
russh · Allocation without limits · CWE-770Affectedrussh
FixNo fix listed yet.
PublishedOct 27, 20:27 · GitHub_M
ScoredOct 27 · 2.3 · GitHub_M
Exploit code publicNone known · checked 21:18 UTC
ExploitedNone known · CISA KEV checked 22:09 UTC
What we know
No known exploitation. CISA KEV, checked 22:09 UTC.
No public exploit code known. Exploit-DB, Metasploit, Nuclei, checked 21:18 UTC.
An attacker only needs network access to the target. No login needed. CVSS: network, no privileges.
It only works under certain conditions, which makes it harder to pull off. CVSS: high attack complexity.
Someone has to open, click or run something first. CVSS: user interaction required.
Description
pageant provides a PageantStream type that implements AsyncRead and AsyncWrite traits and can be used to communicate with a running Pageant instance. From 0.2.0 until 0.2.5, PageantStream::new in pageant/src/wmmessage.rs trusts a peer-controlled four-byte length prefix and buffers until len + 4 bytes are available without checking the fixed _AGENT_MAX_MSGLEN transport capacity. An application that bridges an SSH forwarded-agent channel to the raw stream can allow a malicious server to force large allocations or retain a partially filled frame, causing client memory exhaustion. This issue is fixed in version 0.2.5.
From GitHub_M
Affected and fixed versions
ProductAffectedFixed inrussh>= 0.2.0, < 0.2.5–
Exploit code
Exploit-DBnone knownMetasploitnone knownNucleinone known