# CVE-2026-46673: Russh: Unchecked CryptoVec allocation and growth handling is reachable

> Attackers can cause denial of service via unchecked integer arithmetic in buffer allocation, affecting local agents or remote traffic in older versions.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jun 2026
- **Updated:** 11 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-46673, GHSA-g9f8-wqj9-fjw5, RUSTSEC-2026-0153, RUSTSEC-2026-0154

## What is CVE-2026-46673?

CVE-2026-46673 is a high-severity 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.

### Official description

Russh is a Rust SSH client & server library. Prior to version 0.60.3, CryptoVec used unchecked capacity growth, unchecked length arithmetic, and unsafe allocation/locking paths. In current russh releases, local SSH agent peers could still feed attacker-controlled frame lengths into buffer growth before validation. In older russh releases before 0.58.0, remote SSH traffic also reached CryptoVec through transport and compression buffers. This issue has been patched in version 0.60.3.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-46673?

6 open source packages ship an affected version, including russh and russh-cryptovec.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `russh` | crates.io | All versions | 0.60.3 |
| `russh` | crates.io | All versions | 0.60.3 |
| `russh` | crates.io | From 0.0.0-0 | 0.60.3 |
| `russh-cryptovec` | crates.io | All versions | 0.60.3 |
| `russh-cryptovec` | crates.io | All versions | 0.60.3 |
| `russh-cryptovec` | crates.io | From 0.0.0-0 | 0.60.3 |

## How do I fix CVE-2026-46673?

Upgrade russh to 0.60.3 or later.

## Is CVE-2026-46673 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46673 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46673 and fix it if it is affected.

What it is: CVE-2026-46673 is a high-severity 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46673 exists.

Affected packages and fixed versions:
- russh (crates.io): affected all versions; fixed in 0.60.3
- russh (crates.io): affected all versions; fixed in 0.60.3
- russh (crates.io): affected from 0.0.0-0; fixed in 0.60.3
- russh-cryptovec (crates.io): affected all versions; fixed in 0.60.3
- russh-cryptovec (crates.io): affected all versions; fixed in 0.60.3
- russh-cryptovec (crates.io): affected from 0.0.0-0; fixed in 0.60.3

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46673/ (Markdown: https://insights.sbomify.com/CVE-2026-46673/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46673
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46673
- OSV: https://osv.dev/vulnerability/CVE-2026-46673

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46673/
Summaries are generated and may contain mistakes; the official description above is the record.