Vulnerability in russh-cryptovec (CVE-2026-46673)
Summary
Vulnerability in russh-cryptovec (CVE-2026-46673). Risk of unauthorized operations or information disclosure. Exploitable via CryptoVec. Mitigation: upgrade to 0.60.3 or later.
Original description
The description as published by the source.
Both the SSH agent server and client accepted peer-controlled frame lengths
without enforcing a maximum frame size. This could cause large memory
allocations while parsing a maliciously crafted agent frame.
A malicious peer could advertise an oversized frame length, causing the client
or server to attempt a large memory allocation before validating the frame,
potentially leading to memory exhaustion or process termination.
This is fixed by enforcing a maximum agent frame size of 256 KiB and
rejecting oversized frames before buffer allocation.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-46673 has been found in russh-cryptovec.
Attackers can target a specific entry point like CryptoVec over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade russh-cryptovec to 0.60.3 or later.
If unsure, ask your IT team or search "russh-cryptovec CVE-2026-46673" on the vendor's site.
CVE-2026-46673 (russh-cryptovec) — CWE-770 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: CryptoVec / russh / mlock / munlock
Patched: 0.60.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-770) exists in russh-cryptovec. Attackers reach the vulnerable code path via CryptoVec without authentication.
Check the vendor advisory for the affected versions of russh-cryptovec. Attack surface: CryptoVec / russh / mlock / munlock.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 0.60.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'russh-cryptovec' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'russh-cryptovec' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
russh-cryptovecを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade russh-cryptovec to 0.60.3ステージング環境で 0.60.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-46673 rust-russh Fixed in: 0.64.1-1
References
- advisory rustsec.org
- advisory rustsec.org
- advisory nvd.nist.gov
- package github.com
- package crates.io
- package crates.io
- web github.com
- web github.com
- web github.com