{"answers":{"affected":"2 open source packages ship an affected version, including russh.","exploited":"There is no known exploitation of CVE-2026-102824 in the wild and no public exploit code.","fix":"Upgrade russh to 0.63.0 or later.","what":"CVE-2026-102824 is a medium-severity vulnerability in Eugeny russh, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-102824 and fix it if it is affected.\n\nWhat it is: CVE-2026-102824 is a medium-severity vulnerability in Eugeny russh, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-102824 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- russh (crates.io): affected all versions; fixed in 0.63.0\n- russh (crates.io): affected all versions; fixed in 0.63.0\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-102824/ (Markdown: https://insights.sbomify.com/CVE-2026-102824/index.md)","id":"CVE-2026-102824","markdown":"https://insights.sbomify.com/CVE-2026-102824/index.md","name":"CVE-2026-102824","record":{"aliases":["DEBIAN-CVE-2026-102824","GHSA-w3jg-pjxf-73p4","UBUNTU-CVE-2026-102824"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust SSH library","requires_auth":"low_privilege","summary":"A malicious SSH peer can force the X25519 contribution to zero in hybrid key exchange, weakening cryptographic fallback protection in the Russh library.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"Russh is a Rust SSH client and server library. Prior to 0.63.0, the hybrid ML-KEM 768 and X25519 implementation in russh/src/kex/hybrid_mlkem.rs accepts an all-zero 32-byte peer X25519 public key in both server_dh and compute_shared_secret, forcing the X25519 contribution to the combined shared secret to zero. A malicious SSH peer can therefore make the combined secret depend only on ML-KEM, defeating the hybrid exchange's intended fallback protection if ML-KEM is later weakened. This issue is fixed in version 0.63.0.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Russh: Missing X25519 zero-point validation in hybrid ML-KEM key exchange","id":"CVE-2026-102824","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Russh: Configured server auth-attempt cap is not enforced in the USERAUTH_REQUEST runtime path","id":"CVE-2026-102825"},"packages":[{"ecosystem":"crates.io","fixed":["0.63.0"],"introduced":["0"],"last_affected":[],"package":"russh","purl":null,"source":"GHSA-w3jg-pjxf-73p4"},{"ecosystem":"crates.io","fixed":["0.63.0"],"introduced":["0"],"last_affected":[],"package":"russh","purl":"pkg:cargo/russh","source":"GHSA-w3jg-pjxf-73p4"}],"prev":{"headline":"russh: Client-side channel-scoped Handler callbacks fire for channel IDs the client never opened","id":"CVE-2026-102823"},"products":["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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-30","vendors":["Eugeny"]},"summary":"A malicious SSH peer can force the X25519 contribution to zero in hybrid key exchange, weakening cryptographic fallback protection in the Russh library.","url":"https://insights.sbomify.com/CVE-2026-102824/"}