{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-116775 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-116775 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-116775 is a low-severity vulnerability in Eugeny russh, published on 27 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-116775 and fix it if it is affected.\n\nWhat it is: CVE-2026-116775 is a low-severity vulnerability in Eugeny russh, published on 27 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-116775 in the wild and no public exploit code.\n\nAffected product: Eugeny russh. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-116775/ (Markdown: https://insights.sbomify.com/CVE-2026-116775/index.md)","id":"CVE-2026-116775","markdown":"https://insights.sbomify.com/CVE-2026-116775/index.md","name":"CVE-2026-116775","record":{"aliases":["GHSA-662x-8wvj-2276"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"pageant: unbounded frame buffering on peer-controlled 4-byte length prefix (memory-exhaustion DoS)","id":"CVE-2026-116775","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"USB Test: Heap-based Buffer Overflow in getSectorSize via untrusted DISK_GEOMETRY.BytesPerSector leads to RCE/DoS","id":"CVE-2026-116776"},"packages":[],"prev":{"headline":"russh: peer-declared zero maximum packet size permanently stalls channel writes (silent AsyncWrite hang)","id":"CVE-2026-116774"},"products":["russh"],"published":"2026-10-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-27","vendors":["Eugeny"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-116775/"}