# pageant: Out-of-bounds read / oversized allocation in \`pageant\` MemoryMap::read via a malicious Pageant agent (Windows)

Advisory record · `GHSA-g4mp-vgx3-xrvm`

- **Identifiers:** `GHSA-g4mp-vgx3-xrvm` · `CVE-2026-102820`
- **State:** Confirmed
- **Severity:** CVSS 6.2 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-125](https://cwe.mitre.org/data/definitions/125.html) · [CWE-789](https://cwe.mitre.org/data/definitions/789.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md) · [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 30 Sept 2026
- **Updated:** 1 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 30 Sept 2026, 23:41 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `pageant` (crates.io): affected `<0.2.3`; fixed in `0.2.3`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The pageant crate before 0.2.3 on Windows reads a peer-controlled number of bytes from shared memory without a bounds check. A local process posing as the Pageant SSH agent can crash an SSH client that uses it, trigger a large memory allocation, or sometimes read adjacent memory. Upgrade pageant to 0.2.3 or later.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.2 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0019, the 8th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:24 UTC: First seen by agentprime
- 31 Oct 2026, 14:24 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-g4mp-vgx3-xrvm)

## Sources

- [GitHub Advisory Database: GHSA-g4mp-vgx3-xrvm](https://github.com/advisories/GHSA-g4mp-vgx3-xrvm)
- [OSV: GHSA-g4mp-vgx3-xrvm](https://osv.dev/vulnerability/GHSA-g4mp-vgx3-xrvm)
- <https://github.com/Eugeny/russh/security/advisories/GHSA-g4mp-vgx3-xrvm>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-102820>
- <https://github.com/Eugeny/russh/commit/5d566989ebabfdebfe6b33243d31765a0812260b>
- <https://github.com/Eugeny/russh>
- <https://github.com/Eugeny/russh/releases/tag/v0.63.2>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-g4mp-vgx3-xrvm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-g4mp-vgx3-xrvm/>. Everything for agents: <https://agentprime.io/llms.txt>.