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
Trending — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.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 computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
46.3%
KEV
Not listed

Published

May 20, 2026

Last Modified

May 21, 2026

Advisory Details (4)

Auto-updated Jun 7, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

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 / EcosystemFixed in / 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 rangeFixed inDependents
nimiq-keys———

Weakness Classification(1)

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

Data Freshness Timeline

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

  1. 2026-07-23 03:11 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-17 22:29 UTCOSV refresh
  9. 2026-07-16 17:03 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-13 22:30 UTCEPSS rescore
  14. 2026-07-13 06:13 UTCEPSS rescore
  15. 2026-07-13 06:13 UTCEPSS rescore
  16. 2026-07-12 05:46 UTCEPSS rescore
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-09 19:10 UTCEPSS rescore
  19. 2026-07-08 15:15 UTCEPSS rescore
  20. 2026-07-07 13:46 UTCEPSS rescore
  21. 2026-07-06 16:27 UTCEPSS rescore
  22. 2026-07-06 16:27 UTCEPSS rescore
  23. 2026-07-06 02:23 UTCEPSS rescore
  24. 2026-07-06 02:23 UTCEPSS rescore
  25. 2026-07-05 02:30 UTCEPSS rescore
Show 75 more
  1. 2026-07-04 06:31 UTCEPSS rescore
  2. 2026-07-01 15:06 UTCEPSS rescore
  3. 2026-06-30 23:22 UTCEPSS rescore
  4. 2026-06-29 20:22 UTCGHSA enrichment
  5. 2026-06-29 14:06 UTCEPSS rescore
  6. 2026-06-28 14:07 UTCEPSS rescore
  7. 2026-06-28 07:55 UTCGHSA enrichment
  8. 2026-06-28 04:56 UTCEPSS rescore
  9. 2026-06-27 20:06 UTCGHSA enrichment
  10. 2026-06-27 07:25 UTCGHSA enrichment
  11. 2026-06-27 03:08 UTCEPSS rescore
  12. 2026-06-26 19:29 UTCGHSA enrichment
  13. 2026-06-26 03:43 UTCGHSA enrichment
  14. 2026-06-25 15:01 UTCGHSA enrichment
  15. 2026-06-25 13:49 UTCEPSS rescore
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-24 14:05 UTCEPSS rescore
  18. 2026-06-23 21:33 UTCEPSS rescore
  19. 2026-06-22 14:25 UTCEPSS rescore
  20. 2026-06-22 14:25 UTCEPSS rescore
  21. 2026-06-21 14:56 UTCEPSS rescore
  22. 2026-06-21 14:56 UTCEPSS rescore
  23. 2026-06-21 01:59 UTCEPSS rescore
  24. 2026-06-19 19:25 UTCEPSS rescore
  25. 2026-06-18 17:52 UTCEPSS rescore
  26. 2026-06-18 17:52 UTCEPSS rescore
  27. 2026-06-17 22:40 UTCGHSA enrichment
  28. 2026-06-17 17:53 UTCEPSS rescore
  29. 2026-06-17 11:18 UTCGHSA enrichment
  30. 2026-06-16 21:30 UTCGHSA enrichment
  31. 2026-06-16 17:52 UTCEPSS rescore
  32. 2026-06-16 10:39 UTCGHSA enrichment
  33. 2026-06-15 22:51 UTCGHSA enrichment
  34. 2026-06-15 17:49 UTCEPSS rescore
  35. 2026-06-15 07:51 UTCGHSA enrichment
  36. 2026-06-14 20:10 UTCGHSA enrichment
  37. 2026-06-14 09:14 UTCGHSA enrichment
  38. 2026-06-13 23:00 UTCEPSS rescore
  39. 2026-06-13 22:24 UTCGHSA enrichment
  40. 2026-06-13 07:52 UTCGHSA enrichment
  41. 2026-06-12 23:12 UTCEPSS rescore
  42. 2026-06-12 23:12 UTCEPSS rescore
  43. 2026-06-12 21:00 UTCGHSA enrichment
  44. 2026-06-12 10:10 UTCGHSA enrichment
  45. 2026-06-11 23:19 UTCGHSA enrichment
  46. 2026-06-11 14:00 UTCEPSS rescore
  47. 2026-06-11 12:28 UTCGHSA enrichment
  48. 2026-06-11 01:37 UTCGHSA enrichment
  49. 2026-06-10 22:18 UTCEPSS rescore
  50. 2026-06-10 14:47 UTCGHSA enrichment
  51. 2026-06-10 13:22 UTCEPSS rescore
  52. 2026-06-10 13:22 UTCEPSS rescore
  53. 2026-06-10 03:57 UTCGHSA enrichment
  54. 2026-06-09 17:06 UTCGHSA enrichment
  55. 2026-06-09 06:16 UTCGHSA enrichment
  56. 2026-06-08 19:25 UTCGHSA enrichment
  57. 2026-06-08 14:17 UTCEPSS rescore
  58. 2026-06-08 14:17 UTCEPSS rescore
  59. 2026-06-08 08:17 UTCGHSA enrichment
  60. 2026-06-07 21:26 UTCGHSA enrichment
  61. 2026-06-07 15:25 UTCEPSS rescore
  62. 2026-06-07 15:25 UTCEPSS rescore
  63. 2026-06-07 15:25 UTCEPSS rescore
  64. 2026-06-07 10:36 UTCGHSA enrichment
  65. 2026-06-06 23:46 UTCGHSA enrichment
  66. 2026-06-06 13:47 UTCEPSS rescore
  67. 2026-06-06 13:47 UTCEPSS rescore
  68. 2026-06-06 12:56 UTCGHSA enrichment
  69. 2026-06-06 02:05 UTCGHSA enrichment
  70. 2026-06-05 22:47 UTCEPSS rescore
  71. 2026-06-05 22:47 UTCEPSS rescore
  72. 2026-06-05 15:15 UTCGHSA enrichment
  73. 2026-06-05 06:10 UTCEPSS rescore
  74. 2026-06-05 06:10 UTCEPSS rescore
  75. 2026-06-05 04:24 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 in the National Vulnerability Database on May 20, 2026, with the most recent update on May 21, 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 46.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40092, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs