CVE-2026-46673
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedRussh 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceRussh's CryptoVec implementation contained multiple unsafe operations including unchecked capacity growth, unchecked length arithmetic, and unsafe allocation/locking paths. In current versions, local SSH agent peers could inject attacker-controlled frame lengths into buffer growth before validation. In versions before 0.58.0, remote SSH traffic also reached these unsafe paths through transport and compression buffers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify russh dependencySearch your project's Cargo.lock or Cargo.toml for the 'russh' crate and note its exact version numberAffected if The installed version is any version before 0.60.3 (v0.60.3 and later are fixed)
-
Check for SSH agent peer functionalityInspect your application's code or configuration to determine if it creates an SSH agent listener or accepts local SSH agent socket connectionsAffected if The application accepts SSH agent peer connections and uses a russh version before 0.60.3
-
Verify remote SSH transport handling (versions before 0.58.0)If using russh versions 0.58.0 or higher, this check does not apply; for older versions, determine if the application handles incoming SSH transport or compression buffers from remote connectionsAffected if Using russh version 0.57.x or earlier AND handling remote SSH connections enables the transport/compression buffer attack vector
You are affected if your application depends on russh and uses a version before 0.60.3, especially if it exposes SSH agent socket connections or (for versions before 0.58.0) handles remote SSH traffic.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade russh to version 0.60.3 or later. If unable to upgrade, consider restricting SSH agent access to trusted peers only and implementing network-level controls for SSH connections.
russh version 0.60.3
- Locate the russh dependency in your project's Cargo.toml file
- Update the russh version specification to 0.60.3 or later (e.g., russh = "0.60.3")
- Run `cargo update russh` to fetch the new version
- Run `cargo build` or `cargo check` to verify the upgrade compiles successfully
- Run your test suite to ensure the upgrade does not break existing functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46673 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-46673 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data