CVSS 4.0
2.3 lowCVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NCVE-2026-111062 eugeny russh
Low (2.3) in eugeny russh. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in russh 0.64.0.
On this page
russh is a Rust SSH client and server library. From version 0.34.0-beta.1 until version 0.64.0, its SSH server does not require the signature algorithm in a public-key authentication signature to match the algorithm named in the authentication request. A client possessing an authorized RSA private key can announce rsa-sha2-512 while supplying a valid ssh-rsa SHA-1 signature, bypassing restrictions or producing misleading audit records when applications rely on the requested algorithm. A valid private-key signature remains required, and russh clients are not affected. This issue is fixed in version 0.64.0.
Severity
- EPSS
- 0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-11-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-347 Improper Verification of Cryptographic Signature
- OWASP Top 10
- A04:2025 Cryptographic Failures
- Published
- Modified
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-111062 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-111062?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-111062?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-111062 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-111062)
HTML:
<a href="https://cve.bz/cve/CVE-2026-111062"><img src="https://cve.bz/cve/badge/CVE-2026-111062.svg" alt="CVE-2026-111062"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Eugeny russh | >= 0.34.0-beta.1, < 0.64.0 |
Fix and patched versions
russh(crates.io): fixed in 0.64.0- Debian: fixed package versions per release
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-j7h2-66j4-ghjf | crates.io | russh | >=0.34.0-beta.1 <0.64.0 | 0.64.0 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | rust-russh | 0.64.1-1 | DEBIAN-CVE-2026-111062 |
| Ubuntu | 26.10 | rust-russh | no fix listed | UBUNTU-CVE-2026-111062 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.
Red Hat
Red Hat rates this Low.
This vulnerability is rated as having a Low severity impact because exploitation still requires an attacker to possess an authorized private key, preventing unauthorized access. The flaw allows an authenticated client to supply a valid signature using a weaker algorithm than announced, potentially evading cryptographic policy restrictions or misrepresenting algorithm choices in server audit logs. Only server deployments that enforce specific signature algorithms or rely on requested algorithms for compliance logging are impacted, while client-side usage is unaffected.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Hardened Images | openshell | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-111062.
Attack patterns (CAPEC)
- CAPEC-463 Padding Oracle Crypto Attack Severity: High
- CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.