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 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::from_bytes(sig).unwrap() in the TaggedPublicKey implementation for Ed25519PublicKey. The from_bytes call fails because ed25519_zebra::Signature::try_from 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.
CVE-2026-40092
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-15. NVD baseline CVSS 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 47%
- KEV
- Not listed
Published
May 20, 2026
Last Modified
July 23, 2026
Advisory Details (4)
Auto-updated Jun 7, 2026Unchecked Ed25519 signature length in TaggedPublicKey::verify causes remote node panic via DHT · Advisory · nimiq/core-rs-albatross · GitHub
https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-27w2-87xv-37c6Mainnet 1.4.0
Patch available: nimiq/core-rs-albatross v1.4.0
https://github.com/nimiq/core-rs-albatross/releases/tag/v1.4.0Fix TaggedPublicKey::verify panic on invalid signature length
Patch available: nimiq/core-rs-albatross v1.4.0 (PR #3708 merged 2026-04-22)
https://github.com/nimiq/core-rs-albatross/pull/3708commit 807ee8e99a7c (nimiq/core-rs-albatross)
Patch available: nimiq/core-rs-albatross v1.4.0 (contains commit 807ee8e99a7c)
https://github.com/nimiq/core-rs-albatross/commit/807ee8e99a7ccdc604d49971f292854bfa36754dVendor Advisories for CVE-2026-40092(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| rust | nimiq-keys | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
crates.io(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nimiq-keys | — | — | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 76× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 219 total refreshes for this CVE.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-23 16:52 UTCEG score recompute
- 2026-08-23 16:52 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 22:52 UTCEG score recompute
- 2026-08-21 22:52 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 18:53 UTCEG score recompute
- 2026-08-20 18:53 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 09:50 UTCGHSA enrichment
- 2026-08-16 16:51 UTCEG score recompute
- 2026-08-16 16:51 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 03:28 UTCEG score recompute
- 2026-08-16 03:28 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 23:42 UTCGHSA enrichment
- 2026-08-14 12:50 UTCGHSA enrichment
- 2026-08-14 01:59 UTCEG score recompute
- 2026-08-14 01:59 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 09:37 UTCGHSA enrichment
- 2026-08-12 22:47 UTCEG score recompute
- 2026-08-12 22:47 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 11:57 UTCGHSA enrichment
- 2026-08-12 00:40 UTCGHSA enrichment
- 2026-08-11 13:50 UTCEG score recompute
- 2026-08-11 13:50 UTCGHSA enrichment
- 2026-08-11 13:43 UTCEPSS rescore
- 2026-08-11 00:33 UTCEG score recompute
- 2026-08-11 00:33 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 10:13 UTCGHSA enrichment
- 2026-08-09 23:22 UTCEG score recompute
- 2026-08-09 23:22 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 12:31 UTCGHSA enrichment
- 2026-08-09 01:30 UTCEG score recompute
- 2026-08-09 01:30 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 03:53 UTCGHSA enrichment
- 2026-08-07 17:03 UTCEG score recompute
- 2026-08-07 17:03 UTCGHSA enrichment
- 2026-08-07 06:11 UTCGHSA enrichment
- 2026-08-06 19:09 UTCEG score recompute
- 2026-08-06 19:09 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 08:19 UTCGHSA enrichment
- 2026-08-05 21:15 UTCEG score recompute
- 2026-08-05 21:15 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-04 03:43 UTCGHSA enrichment
- 2026-08-03 16:52 UTCEG score recompute
- 2026-08-03 16:52 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 02:09 UTCGHSA enrichment
- 2026-08-02 15:19 UTCGHSA enrichment
- 2026-08-02 04:27 UTCEG score recompute
- 2026-08-02 04:27 UTCGHSA enrichment
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 17:36 UTCEG score recompute
- 2026-08-01 17:36 UTCGHSA enrichment
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 18:04 UTCEG score recompute
- 2026-07-29 18:04 UTCGHSA enrichment
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 08:13 UTCEG score recompute
- 2026-07-26 08:13 UTCGHSA enrichment
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:11 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 22:29 UTCOSV refresh
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
Frequently asked(5)
What is CVE-2026-40092?
When was CVE-2026-40092 disclosed?
Is CVE-2026-40092 actively exploited?
What is the CVSS score of CVE-2026-40092?
How do I remediate CVE-2026-40092?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-40092
Is Your Infrastructure Affected by CVE-2026-40092?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.