rustsec-2026-0153
Vulnerability from osv_rustsec
CryptoVec used unchecked capacity growth, unchecked length arithmetic, and
unsafe allocation and locking paths. In affected russh releases,
attacker-controlled input could reach these code paths through buffer resizing
operations.
Two affected reachability paths were identified:
-
Current
russhreleases (0.60.xbefore the fix) Local SSH agent peers could provide attacker-controlled frame lengths that were used to resize internal buffers before validation in: -
AgentClient::read_response -
agent::server::Connection::run -
Historical
russhreleases before0.58.0CryptoVecwas also used for non-secret transport and compression buffers, allowing remote SSH traffic to triggerCryptoVecgrowth through: -
transport packet reads
- zlib decompression output
These remote paths were removed in 0.58.0 when CryptoVec stopped being used
for those buffers.
Under constrained memory conditions, historical russh versions prior to
0.58.0 can abort the process when remote compressed payload expansion causes
allocation failure in CryptoVec. This was reproduced through the compression
path and resulted in process termination in the Unix allocation/locking
implementation after null pointer allocation failure.
For current affected releases, oversized local SSH agent frame lengths could trigger untrusted-input-driven buffer growth prior to validation.
No practical remote code execution, integrity or confidentiality impact has been demonstrated.
Fixed by validating CryptoVec growth operations and rejecting oversized SSH agent frame lengths before buffer allocation.
{
"affected": [
{
"database_specific": {
"categories": [
"denial-of-service"
],
"cvss": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"informational": null
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "russh-cryptovec",
"purl": "pkg:cargo/russh-cryptovec"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-0"
},
{
"fixed": "0.60.3"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"CVE-2026-46673",
"GHSA-g9f8-wqj9-fjw5"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "`CryptoVec` used unchecked capacity growth, unchecked length arithmetic, and\nunsafe allocation and locking paths. In affected `russh` releases,\nattacker-controlled input could reach these code paths through buffer resizing\noperations.\n\nTwo affected reachability paths were identified:\n\n* **Current `russh` releases (`0.60.x` before the fix)**\n Local SSH agent peers could provide attacker-controlled frame lengths that\n were used to resize internal buffers before validation in:\n\n * `AgentClient::read_response`\n * `agent::server::Connection::run`\n\n* **Historical `russh` releases before `0.58.0`**\n `CryptoVec` was also used for non-secret transport and compression buffers,\n allowing remote SSH traffic to trigger `CryptoVec` growth through:\n\n * transport packet reads\n * zlib decompression output\n\nThese remote paths were removed in `0.58.0` when `CryptoVec` stopped being used\nfor those buffers.\n\nUnder constrained memory conditions, historical `russh` versions prior to\n`0.58.0` can abort the process when remote compressed payload expansion causes\nallocation failure in `CryptoVec`. This was reproduced through the compression\npath and resulted in process termination in the Unix allocation/locking\nimplementation after null pointer allocation failure.\n\nFor current affected releases, oversized local SSH agent frame lengths could\ntrigger untrusted-input-driven buffer growth prior to validation.\n\nNo practical remote code execution, integrity or confidentiality impact has\nbeen demonstrated.\n\nFixed by validating CryptoVec growth operations and rejecting oversized SSH\nagent frame lengths before buffer allocation.",
"id": "RUSTSEC-2026-0153",
"modified": "2026-06-02T09:53:13Z",
"published": "2026-05-15T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/russh-cryptovec"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2026-0153.html"
},
{
"type": "ADVISORY",
"url": "https://github.com/Eugeny/russh/security/advisories/GHSA-g9f8-wqj9-fjw5"
},
{
"type": "WEB",
"url": "https://github.com/Eugeny/russh/commit/a2d48a71fe93d18cbd666c8d53d0882f5ce110c4"
}
],
"related": [],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "Unchecked `CryptoVec` allocation and growth handling"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.