CVE-2026-102820: Eugeny russh · Out-of-bounds Read
Affects Eugeny russhSource CVE Database V5
Not known to be exploited · CVSS 6.2 Medium : upgrade to 0.63.2 when convenient.
Data as of 13 Nov 2026, 23:53 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.63.2, 0.2.3
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 29 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Upgrade russh to 0.63.2; pageant to 0.2.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Eugenyrussh | Affected
| Fixed in
|
| rustpageant | Affected
| Fixed in
|
crates.iorusshpkg:cargo/russhOther threats | Affected
| Fixed in
|
crates.iopageantpkg:cargo/pageantOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to pageant version 0.2.3 or later, where this vulnerability is fixed. No other mitigations are indicated. Since this is a local vulnerability, restricting local access to trusted users can reduce risk until patched.
Description
CVE-2026-102820 is an out-of-bounds read vulnerability in the Windows pageant crate used by Eugeny's russh library. The flaw exists in the MemoryMap::read function prior to pageant version 0.2.3, where a peer-controlled 32-bit response length is trusted, allowing a local process impersonating the Pageant window to cause a large memory allocation and read beyond the mapped memory. This can crash the russh client and potentially expose adjacent committed memory. The issue is fixed in pageant 0.2.3.