https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 15:16:26 +0000 https://vulnerability.circl.lu/sighting/430b83b7-1d02-4637-a4b4-f6468db8fb13/export {"uuid": "430b83b7-1d02-4637-a4b4-f6468db8fb13", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-102820", "type": "seen", "source": "https://gist.github.com/alon710/b6f4cdc8370bc7031705c8ea315cfc78", "content": "# CVE-2026-102820: CVE-2026-102820: Out-of-Bounds Read and Excessive Memory Allocation in russh pageant\n\n> **CVSS Score:** 6.2\n> **Published:** 2026-09-30\n> **Full Report:** https://cvereports.com/reports/CVE-2026-102820\n\n## Summary\nA critical memory handling vulnerability exists in the pageant crate, a workspace component of the Rust-based russh SSH client library, during communication with the PuTTY Pageant SSH agent on Windows systems. Prior to version 0.2.3, the library's shared memory parsing logic blindly trusted a peer-controlled, 32-bit big-endian response length field. This allows local attackers running within the same user session to trigger out-of-bounds reads or execute an out-of-memory crash of the client application.\n\n## TL;DR\nUnvalidated 32-bit response length fields in the pageant crate allow a local process to cause an out-of-memory crash or perform out-of-bounds reads against russh-based clients.\n\n## Technical Details\n\n- **CWE ID**: CWE-125, CWE-789\n- **Attack Vector**: Local\n- **CVSS v3.1 Score**: 6.2 (Medium)\n- **EPSS Score**: 0.00129 (0.129% probability)\n- **Impact**: Denial of Service (DoS) and potential Information Disclosure\n- **Exploit Status**: poc\n- **KEV Status**: Not Listed\n\n## Affected Systems\n\n- pageant crate on Windows operating systems\n- russh client library integrations on Windows operating systems\n- **pageant**: < 0.2.3 (Fixed in: `0.2.3`)\n- **russh**: >= 0.58.0, < 0.63.2 (Fixed in: `0.63.2`)\n\n## Mitigation\n\n- Update the cargo project dependencies immediately to use patched versions of the pageant and russh libraries.\n- Isolate automated SSH tasks on Windows within separate containerized virtual contexts to avoid local window messaging interference.\n- Utilize cargo-audit in build pipelines to block deployment of vulnerable dependencies.\n\n**Remediation Steps:**\n1. Locate the cargo workspace file containing dependencies on the pageant or russh crates.\n2. Run 'cargo update -p pageant' and 'cargo update -p russh' to update to fixed versions.\n3. Verify that pageant is updated to at least 0.2.3 and russh is updated to at least 0.63.2.\n4. Run 'cargo audit' to ensure that no further references to the vulnerable library versions remain in your local dependency trees.\n\n## References\n\n- [GitHub Security Advisory](https://github.com/Eugeny/russh/security/advisories/GHSA-g4mp-vgx3-xrvm)\n- [Fix Patch Commit](https://github.com/Eugeny/russh/commit/5d566989ebabfdebfe6b33243d31765a0812260b)\n- [NVD CVE Entry](https://nvd.nist.gov/vuln/detail/CVE-2026-102820)\n- [CVE.org Record](https://www.cve.org/CVERecord?id=CVE-2026-102820)\n\n\n---\n*Generated by [CVEReports](https://cvereports.com/reports/CVE-2026-102820) - Automated Vulnerability Intelligence*", "creation_timestamp": "2026-10-01T13:30:28.000000Z"} {"uuid": "430b83b7-1d02-4637-a4b4-f6468db8fb13", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-102820", "type": "seen", "source": "https://gist.github.com/alon710/b6f4cdc8370bc7031705c8ea315cfc78", "content": "# CVE-2026-102820: CVE-2026-102820: Out-of-Bounds Read and Excessive Memory Allocation in russh pageant\n\n> **CVSS Score:** 6.2\n> **Published:** 2026-09-30\n> **Full Report:** https://cvereports.com/reports/CVE-2026-102820\n\n## Summary\nA critical memory handling vulnerability exists in the pageant crate, a workspace component of the Rust-based russh SSH client library, during communication with the PuTTY Pageant SSH agent on Windows systems. Prior to version 0.2.3, the library's shared memory parsing logic blindly trusted a peer-controlled, 32-bit big-endian response length field. This allows local attackers running within the same user session to trigger out-of-bounds reads or execute an out-of-memory crash of the client application.\n\n## TL;DR\nUnvalidated 32-bit response length fields in the pageant crate allow a local process to cause an out-of-memory crash or perform out-of-bounds reads against russh-based clients.\n\n## Technical Details\n\n- **CWE ID**: CWE-125, CWE-789\n- **Attack Vector**: Local\n- **CVSS v3.1 Score**: 6.2 (Medium)\n- **EPSS Score**: 0.00129 (0.129% probability)\n- **Impact**: Denial of Service (DoS) and potential Information Disclosure\n- **Exploit Status**: poc\n- **KEV Status**: Not Listed\n\n## Affected Systems\n\n- pageant crate on Windows operating systems\n- russh client library integrations on Windows operating systems\n- **pageant**: < 0.2.3 (Fixed in: `0.2.3`)\n- **russh**: >= 0.58.0, < 0.63.2 (Fixed in: `0.63.2`)\n\n## Mitigation\n\n- Update the cargo project dependencies immediately to use patched versions of the pageant and russh libraries.\n- Isolate automated SSH tasks on Windows within separate containerized virtual contexts to avoid local window messaging interference.\n- Utilize cargo-audit in build pipelines to block deployment of vulnerable dependencies.\n\n**Remediation Steps:**\n1. Locate the cargo workspace file containing dependencies on the pageant or russh crates.\n2. Run 'cargo update -p pageant' and 'cargo update -p russh' to update to fixed versions.\n3. Verify that pageant is updated to at least 0.2.3 and russh is updated to at least 0.63.2.\n4. Run 'cargo audit' to ensure that no further references to the vulnerable library versions remain in your local dependency trees.\n\n## References\n\n- [GitHub Security Advisory](https://github.com/Eugeny/russh/security/advisories/GHSA-g4mp-vgx3-xrvm)\n- [Fix Patch Commit](https://github.com/Eugeny/russh/commit/5d566989ebabfdebfe6b33243d31765a0812260b)\n- [NVD CVE Entry](https://nvd.nist.gov/vuln/detail/CVE-2026-102820)\n- [CVE.org Record](https://www.cve.org/CVERecord?id=CVE-2026-102820)\n\n\n---\n*Generated by [CVEReports](https://cvereports.com/reports/CVE-2026-102820) - Automated Vulnerability Intelligence*", "creation_timestamp": "2026-10-01T13:30:28.000000Z"} https://vulnerability.circl.lu/sighting/430b83b7-1d02-4637-a4b4-f6468db8fb13/export Thu, 01 Oct 2026 13:30:28 +0000 https://vulnerability.circl.lu/sighting/91a8901a-2652-403e-b864-c6cb196febe4/export {"uuid": "91a8901a-2652-403e-b864-c6cb196febe4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2026-102820", "type": "published-proof-of-concept", "source": "https://github.com/Eugeny/russh/security/advisories/GHSA-g4mp-vgx3-xrvm", "content": "", "creation_timestamp": "2026-09-03T18:37:41.000000Z"} {"uuid": "91a8901a-2652-403e-b864-c6cb196febe4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2026-102820", "type": "published-proof-of-concept", "source": "https://github.com/Eugeny/russh/security/advisories/GHSA-g4mp-vgx3-xrvm", "content": "", "creation_timestamp": "2026-09-03T18:37:41.000000Z"} https://vulnerability.circl.lu/sighting/91a8901a-2652-403e-b864-c6cb196febe4/export Thu, 03 Sep 2026 18:37:41 +0000