CVE-2026-34066

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2026-04-22. NVD baseline CVSS 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 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. Prior to version 1.3.0, HistoryStore::put_historic_txns uses an assert! to enforce invariants about HistoricTransaction.block_number (must be within the macro block being pushed and within the same epoch). During history sync, a peer can influence the history: &[HistoricTransaction] input passed into Blockchain::push_history_sync, and a malformed history list can violate these invariants and trigger a panic. extend_history_sync calls this.history_store.add_to_history(..) before comparing the computed history root against the macro block header (block.history_root()), so the panic can happen before later rejection checks run. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
24(Track)
EG Risk 24/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
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

April 22, 2026

Last Modified

April 24, 2026

Advisory Details (4)

Auto-updated Aug 2, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr, github_release.
github Patch Available🟡 PoC Available

Peer-triggerable panic during history sync · Advisory · nimiq/core-rs-albatross · GitHub

https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-j99g-7rqw-q9jg
github_release Patch Available

Mainnet 1.3.0

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

https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0
github_pr

Fix peer-triggerable panic during history sync

Upstream fix in progress (PR #3656 · nimiq/core-rs-albatross, state=closed)

https://github.com/nimiq/core-rs-albatross/pull/3656
github_commit Patch Available

commit 6f5511309c19 (nimiq/core-rs-albatross)

Patch available: nimiq/core-rs-albatross v1.3.0 (contains commit 6f5511309c19)

https://github.com/nimiq/core-rs-albatross/commit/6f5511309c199d84b012fe6b9aba7e5582892c50

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
rustnimiq-blockchain—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-blockchain———

Weakness Classification(3)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-34066?
CVE-2026-34066 is a medium vulnerability published on April 22, 2026. nimiq-blockchain provides persistent block storage for Nimiq's Rust implementation. Prior to version 1.3.0, HistoryStore::puthistorictxns uses an assert! to enforce invariants about HistoricTransaction.blocknumber (must be within the macro block being pushed and within the same epoch). During…
When was CVE-2026-34066 disclosed?
CVE-2026-34066 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on April 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-34066 actively exploited?
CVE-2026-34066 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.6% of all scored CVEs.
What is the CVSS score of CVE-2026-34066?
CVE-2026-34066 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-34066?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-34066, 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-34066

Explore →

Is Your Infrastructure Affected by CVE-2026-34066?

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

Start Free Scan →Browse All CVEs