{"answers":{"affected":"2 open source packages ship an affected version, including russh.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46705 exists.","fix":"Upgrade russh to 0.61.0 or later.","what":"CVE-2026-46705 is a medium-severity authentication bypass vulnerability in Eugeny russh, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-46705 and fix it if it is affected.\n\nWhat it is: CVE-2026-46705 is a medium-severity authentication bypass vulnerability in Eugeny russh, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46705 exists.\n\nAffected packages and fixed versions:\n- russh (crates.io): affected from 0.34.0-beta.1; fixed in 0.61.0\n- russh (crates.io): affected from 0.34.0-beta.1; fixed in 0.61.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-46705/ (Markdown: https://insights.sbomify.com/CVE-2026-46705/index.md)","id":"CVE-2026-46705","markdown":"https://insights.sbomify.com/CVE-2026-46705/index.md","name":"CVE-2026-46705","record":{"aliases":["DEBIAN-CVE-2026-46705","GHSA-hpv4-5h6f-wqr3"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust SSH library","requires_auth":"none","summary":"Attackers can bypass authentication checks in russh SSH servers by exploiting state persistence when changing user or service names during login.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Russh is a Rust SSH client \u0026 server library. From version 0.34.0-beta.1 to before version 0.61.0, the russh server authentication path keeps internal userauth state across SSH_MSG_USERAUTH_REQUEST messages without separating that state when the request principal changes. RFC 4252 allows the user name and service name fields to change between authentication requests. The issue is not that such changes are invalid. The issue is that russh-owned authentication state, such as remaining methods, partial-success state, and in-progress method state, can remain associated with the connection and then influence a later request for a different (user, service). This is an internal library state mismatch. This issue has been patched in version 0.61.0.","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":"russh server userauth state is not reset when authentication principal changes","id":"CVE-2026-46705","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"EspoCRM: Target list Opt-Out actions allows opting out record without access Target List and access to record","id":"CVE-2026-46708"},"packages":[{"ecosystem":"crates.io","fixed":["0.61.0"],"introduced":["0.34.0-beta.1"],"last_affected":[],"package":"russh","purl":null,"source":"GHSA-hpv4-5h6f-wqr3"},{"ecosystem":"crates.io","fixed":["0.61.0"],"introduced":["0.34.0-beta.1"],"last_affected":[],"package":"russh","purl":"pkg:cargo/russh","source":"GHSA-hpv4-5h6f-wqr3"}],"prev":{"headline":"BoxLite: Path Traversal Vulnerability in boxlite Leads to Arbitrary File Write on the Host","id":"CVE-2026-46703"},"products":["russh"],"published":"2026-06-10","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-11","vendors":["Eugeny"]},"summary":"Attackers can bypass authentication checks in russh SSH servers by exploiting state persistence when changing user or service names during login.","url":"https://insights.sbomify.com/CVE-2026-46705/"}