{"answers":{"affected":"2 open source packages ship an affected version, including pageant.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102820 exists.","fix":"Upgrade pageant to 0.2.3 or later.","what":"CVE-2026-102820 is a medium-severity memory corruption vulnerability in Eugeny pageant, published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-102820 and fix it if it is affected.\n\nWhat it is: CVE-2026-102820 is a medium-severity memory corruption vulnerability in Eugeny pageant, published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102820 exists.\n\nAffected packages and fixed versions:\n- pageant (crates.io): affected all versions; fixed in 0.2.3\n- pageant (crates.io): affected all versions; fixed in 0.2.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-102820/ (Markdown: https://insights.sbomify.com/CVE-2026-102820/index.md)","id":"CVE-2026-102820","markdown":"https://insights.sbomify.com/CVE-2026-102820/index.md","name":"CVE-2026-102820","record":{"aliases":["DEBIAN-CVE-2026-102820","GHSA-g4mp-vgx3-xrvm","UBUNTU-CVE-2026-102820"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rust Pageant library","requires_auth":"none","summary":"A malicious local Pageant agent can trigger an out-of-bounds read and oversized allocation in the Rust pageant library, causing crashes or memory exposure.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-789","name":"Memory Allocation with Excessive Size Value"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"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.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"pageant: Out-of-bounds read / oversized allocation in `pageant` MemoryMap::read via a malicious Pageant agent (Windows)","id":"CVE-2026-102820","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Russh: Unbounded memory exhaustion via CHANNEL_OPEN flood during a client-stalled rekey","id":"CVE-2026-102821"},"packages":[{"ecosystem":"crates.io","fixed":["0.2.3"],"introduced":["0"],"last_affected":[],"package":"pageant","purl":null,"source":"GHSA-g4mp-vgx3-xrvm"},{"ecosystem":"crates.io","fixed":["0.2.3"],"introduced":["0"],"last_affected":[],"package":"pageant","purl":"pkg:cargo/pageant","source":"GHSA-g4mp-vgx3-xrvm"}],"prev":{"headline":"Unauthenticated Wireless Regulatory Region Configuration in TP-Link RE305","id":"CVE-2026-102816"},"products":["pageant","russh"],"published":"2026-09-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-30","vendors":["Eugeny","rust"]},"summary":"A malicious local Pageant agent can trigger an out-of-bounds read and oversized allocation in the Rust pageant library, causing crashes or memory exposure.","url":"https://insights.sbomify.com/CVE-2026-102820/"}