CVE-2026-40092
- Source
- https://cve.org/CVERecord?id=CVE-2026-40092
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-40092.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-40092
- Aliases
- Published
- 2026-05-20T21:16:40.805Z
- Modified
- 2026-07-08T08:12:33.719948357Z
- Severity
-
- 7.5 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
- Summary
- nimiq-keys: Unchecked Ed25519 signature length in TaggedPublicKey::verify causes remote node panic via DHT
- Details
-
nimiq-blockchain provides persistent block storage for Nimiq's Rust implementation. In versions 1.3.0 and below, a malicious network peer can crash any Nimiq full node by publishing a crafted Kademlia DHT record. The maliciously crafted record would contain a TaggedSigned<ValidatorRecord, KeyPair> with a signature field whose byte length is not exactly 64 in order to cause a crash. When the victim node's DHT verifier calls TaggedSigned::verify, execution reaches Ed25519Signature::frombytes(sig).unwrap() in the TaggedPublicKey implementation for Ed25519PublicKey. The frombytes call fails because ed25519zebra::Signature::tryfrom rejects slices not 64 bytes, and the unwrap() panics. The BLS TaggedPublicKey implementation correctly returns false on error; only the Ed25519 implementation panics. This issue has been fixed in version 1.4.0.
- Database specific
{ "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/40xxx/CVE-2026-40092.json", "cwe_ids": [ "CWE-252" ], "cna_assigner": "GitHub_M" }- References
-
- https://github.com/nimiq/core-rs-albatross/releases/tag/v1.4.0
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/40xxx/CVE-2026-40092.json
- https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-27w2-87xv-37c6
- https://nvd.nist.gov/vuln/detail/CVE-2026-40092
- https://github.com/nimiq/core-rs-albatross/commit/807ee8e99a7ccdc604d49971f292854bfa36754d
- https://github.com/nimiq/core-rs-albatross/pull/3708