CVE-2026-40092

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-15. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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 computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
0.8%
EPSS %ILE
53rd
KEV
Not listed

Published

May 20, 2026

Last Modified

July 23, 2026

Advisory Details (4)

Auto-updated Jun 7, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
githubMentions a patch (unverified)

Unchecked 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-37c6
github_release Patch Available

Mainnet 1.4.0

Patch available: nimiq/core-rs-albatross v1.4.0

https://github.com/nimiq/core-rs-albatross/releases/tag/v1.4.0
github_pr Patch Available

Fix 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/3708
github_commit Patch Available

commit 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/807ee8e99a7ccdc604d49971f292854bfa36754d

Vendor 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 / EcosystemFix (by version range) / PatchReleasedSource
rustnimiq-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)
PackageVulnerable rangeFix by version rangeDependents
nimiq-keys—
  • every version through 0.2.0: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 26× 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 257 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:17 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-30 03:10 UTCOSV refresh
  11. 2026-09-27 13:48 UTCEPSS rescore
  12. 2026-09-26 15:58 UTCEPSS rescore
  13. 2026-09-26 00:26 UTCEPSS rescore
  14. 2026-09-20 20:15 UTCEPSS rescore
  15. 2026-09-18 19:28 UTCEPSS rescore
  16. 2026-09-18 19:28 UTCEPSS rescore
  17. 2026-09-17 19:30 UTCEPSS rescore
  18. 2026-09-16 14:08 UTCEPSS rescore
  19. 2026-09-16 05:15 UTCEPSS rescore
  20. 2026-09-15 03:11 UTCEPSS rescore
  21. 2026-09-13 16:47 UTCEPSS rescore
  22. 2026-09-12 15:01 UTCEPSS rescore
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-11 09:37 UTCEPSS rescore
  25. 2026-09-11 05:23 UTCOSV refresh
Show 75 more
  1. 2026-09-10 09:34 UTCEPSS rescore
  2. 2026-09-08 22:00 UTCEPSS rescore
  3. 2026-09-07 16:01 UTCEPSS rescore
  4. 2026-09-06 13:47 UTCEPSS rescore
  5. 2026-09-04 05:06 UTCEPSS rescore
  6. 2026-09-02 14:12 UTCEPSS rescore
  7. 2026-09-01 13:53 UTCEPSS rescore
  8. 2026-09-01 04:39 UTCEPSS rescore
  9. 2026-08-30 19:17 UTCEPSS rescore
  10. 2026-08-30 01:22 UTCEPSS rescore
  11. 2026-08-28 21:41 UTCEPSS rescore
  12. 2026-08-27 14:25 UTCEPSS rescore
  13. 2026-08-26 14:46 UTCEPSS rescore
  14. 2026-08-25 13:49 UTCEPSS rescore
  15. 2026-08-23 16:52 UTCEG score recompute
  16. 2026-08-23 16:52 UTCGHSA enrichment
  17. 2026-08-23 00:19 UTCEPSS rescore
  18. 2026-08-21 23:49 UTCEPSS rescore
  19. 2026-08-21 22:52 UTCEG score recompute
  20. 2026-08-21 22:52 UTCGHSA enrichment
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-20 18:53 UTCEG score recompute
  23. 2026-08-20 18:53 UTCGHSA enrichment
  24. 2026-08-19 17:03 UTCEPSS rescore
  25. 2026-08-18 13:48 UTCEPSS rescore
  26. 2026-08-17 13:47 UTCEPSS rescore
  27. 2026-08-17 09:50 UTCGHSA enrichment
  28. 2026-08-16 16:51 UTCEG score recompute
  29. 2026-08-16 16:51 UTCGHSA enrichment
  30. 2026-08-16 14:56 UTCEPSS rescore
  31. 2026-08-16 03:28 UTCEG score recompute
  32. 2026-08-16 03:28 UTCGHSA enrichment
  33. 2026-08-16 02:14 UTCEPSS rescore
  34. 2026-08-15 01:30 UTCEPSS rescore
  35. 2026-08-14 23:42 UTCGHSA enrichment
  36. 2026-08-14 12:50 UTCGHSA enrichment
  37. 2026-08-14 01:59 UTCEG score recompute
  38. 2026-08-14 01:59 UTCGHSA enrichment
  39. 2026-08-13 22:00 UTCEPSS rescore
  40. 2026-08-13 09:37 UTCGHSA enrichment
  41. 2026-08-12 22:47 UTCEG score recompute
  42. 2026-08-12 22:47 UTCGHSA enrichment
  43. 2026-08-12 13:51 UTCEPSS rescore
  44. 2026-08-12 11:57 UTCGHSA enrichment
  45. 2026-08-12 00:40 UTCGHSA enrichment
  46. 2026-08-11 13:50 UTCEG score recompute
  47. 2026-08-11 13:50 UTCGHSA enrichment
  48. 2026-08-11 13:43 UTCEPSS rescore
  49. 2026-08-11 00:33 UTCEG score recompute
  50. 2026-08-11 00:33 UTCGHSA enrichment
  51. 2026-08-11 00:00 UTCEPSS rescore
  52. 2026-08-10 10:13 UTCGHSA enrichment
  53. 2026-08-09 23:22 UTCEG score recompute
  54. 2026-08-09 23:22 UTCGHSA enrichment
  55. 2026-08-09 13:46 UTCEPSS rescore
  56. 2026-08-09 12:31 UTCGHSA enrichment
  57. 2026-08-09 01:30 UTCEG score recompute
  58. 2026-08-09 01:30 UTCGHSA enrichment
  59. 2026-08-08 16:37 UTCEPSS rescore
  60. 2026-08-08 03:53 UTCGHSA enrichment
  61. 2026-08-07 17:03 UTCEG score recompute
  62. 2026-08-07 17:03 UTCGHSA enrichment
  63. 2026-08-07 06:11 UTCGHSA enrichment
  64. 2026-08-06 19:09 UTCEG score recompute
  65. 2026-08-06 19:09 UTCGHSA enrichment
  66. 2026-08-06 13:46 UTCEPSS rescore
  67. 2026-08-06 08:19 UTCGHSA enrichment
  68. 2026-08-05 21:15 UTCEG score recompute
  69. 2026-08-05 21:15 UTCGHSA enrichment
  70. 2026-08-05 19:17 UTCEPSS rescore
  71. 2026-08-04 15:10 UTCEPSS rescore
  72. 2026-08-04 10:38 UTCEPSS rescore
  73. 2026-08-04 03:43 UTCGHSA enrichment
  74. 2026-08-03 16:52 UTCEG score recompute
  75. 2026-08-03 16:52 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-40092?
CVE-2026-40092 is a high vulnerability published on May 20, 2026. 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>…
When was CVE-2026-40092 disclosed?
CVE-2026-40092 was first published on May 20, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40092 actively exploited?
CVE-2026-40092 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-40092?
CVE-2026-40092 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-40092?
A fix for CVE-2026-40092 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-40092 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-40092

Explore →

Is Your Infrastructure Affected by CVE-2026-40092?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.