nimiq/core-rs-albatross: Discovery handshake limit could underflow and later provoke a deterministic overflow panic
nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, the discovery handler accepts a peer-controlled limit during handshake and stores it unchanged. The immediate HandshakeAck path then honors limit = 0 and returns zero contacts, which makes the session look benign. Later, after the same session reaches Established, the periodic update path computes self.peer_list_limit.unwrap() as usize - 1. With limit = 0, that wraps to usize::MAX and then in rand 0.9.2, choose_multiple() immediately attempts Vec::with_capacity(amount), which deterministically panics with capacity overflow. This issue has been patched in version 1.3.0.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-33184
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 01:07 UTC · Revision 1
Source evidence
nimiq/core-rs-albatross: Discovery handshake limit could underflow and later provoke a deterministic overflow panic
core-osv · Original sourcePublished 3 Apr 2026, 22:09 UTC
nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, the discovery handler accepts a peer-controlled limit during handshake and stores it unchanged. The immediate HandshakeAck path then honors limit = 0 and returns zero contacts, which makes the session look benign. Later, after the same session reaches Established, the periodic update path computes self.peer_list_limit.unwrap() as usize - 1. With limit = 0, that wraps to usize::MAX and then in rand 0.9.2, choose_multiple() immediately attempts Vec::with_capacity(amount), which deterministically panics with capacity overflow. This issue has been patched in version 1.3.0.
osv:CVE-2026-33184
Complete source record
{
"id": "0b18d0b3f1cecc9a2752ca034cb977fd5c28ddb8d2861c2d8c4c0e7cae0b26c9",
"url": "https://osv.dev/vulnerability/CVE-2026-33184",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "nimiq/core-rs-albatross: Discovery handshake limit could underflow and later provoke a deterministic overflow panic",
"summary": "nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, the discovery handler accepts a peer-controlled limit during handshake and stores it unchanged. The immediate HandshakeAck path then honors limit = 0 and returns zero contacts, which makes the session look benign. Later, after the same session reaches Established, the periodic update path computes self.peer_list_limit.unwrap() as usize - 1. With limit = 0, that wraps to usize::MAX and then in rand 0.9.2, choose_multiple() immediately attempts Vec::with_capacity(amount), which deterministically panics with capacity overflow. This issue has been patched in version 1.3.0.",
"evidence": "osv:CVE-2026-33184",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-33184",
"aliases": [
"CVE-2026-33184",
"GHSA-5rm9-893q-vmhm"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/nimiq/core-rs-albatross",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "8f60a2d75b74b55764ecf34bd4435f4961630595"
},
{
"fixed": "5bd15d9af710abeecdfb63d0a721dc883efb59c4"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:nimiq:nimiq_proof-of-stake:*:*:*:*:*:rust:*:*",
"range": [
{
"introduced": "0"
},
{
"last_affected": "1.2.2"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "8f60a2d75b74b55764ecf34bd4435f4961630595"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "5bd15d9af710abeecdfb63d0a721dc883efb59c4"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v1.3.0"
}
]
}
}
],
"versions": [
"v1.2.2",
"v1.2.1",
"v1.2.0",
"v1.1.1",
"v1.1.0",
"v1.0.9",
"v1.0.8",
"v1.0.7",
"v1.0.6",
"v1.0.5",
"v1.0.4",
"v1.0.3",
"v1.0.2",
"v1.0.1",
"v1.0.0",
"v1.0.0-rc.5",
"v1.0.0-rc.4",
"v1.0.0-rc.3",
"v1.0.0-rc.2",
"v1.0.0-rc.1",
"v1.0.0-rc.0",
"v0.24.4",
"v0.24.3",
"v0.24.2",
"v0.24.1",
"v0.24.0",
"v0.23.0",
"v0.22.3",
"v0.22.2",
"v0.22.1",
"v0.22.0",
"v0.21.1",
"v0.21.0",
"v0.20.5",
"v0.20.4",
"v0.20.3",
"v0.20.2",
"v0.20.1",
"v0.20.0",
"v0.19.0",
"v0.18.0",
"v0.17.0",
"v0.16.1",
"v0.16.0",
"v0.15.0",
"v0.14.0",
"v0.13.1",
"v0.13.0",
"v0.12.1",
"v0.12.0",
"v0.11.5",
"v0.11.4",
"v0.11.3",
"v0.11.2",
"v0.11.1",
"v0.11.0",
"v0.10.0",
"v0.9.0",
"v0.8.3",
"v0.8.2",
"v0.8.1",
"v0.8.0",
"v0.7.0",
"v0.6.0",
"v0.5.4",
"v0.5.3",
"v0.5.2",
"v0.5.1",
"v0.5.0",
"v0.4.1",
"v0.4.0",
"v0.3.3",
"v0.3.2",
"v0.3.1",
"v0.3.0",
"v0.2.2",
"v0.2.1",
"v0.2.0",
"v0.1.0",
"v0.1.0-rc.3",
"v0.1.0-rc.2",
"v0.1.0-rc.1",
"v0.1.0-rc.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-33184.json"
}
}
],
"modified": "2026-10-28T02:30:48.673034393Z",
"provider": "osv",
"references": [
"https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/33xxx/CVE-2026-33184.json",
"https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-5rm9-893q-vmhm",
"https://nvd.nist.gov/vuln/detail/CVE-2026-33184",
"https://github.com/nimiq/core-rs-albatross/commit/8f60a2d75b74b55764ecf34bd4435f4961630595",
"https://github.com/nimiq/core-rs-albatross/pull/3664"
],
"provider_metadata": {
"cwe_ids": [
"CWE-191"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/33xxx/CVE-2026-33184.json"
}
},
"related_cves": [
{
"value": "CVE-2026-33184",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 516850,
"published_at": "2026-04-03T22:09:01.43+00:00"
}