CVE-2026-46369

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 67% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
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%CVSS: 7.5Exploit: None knownExposed: 0

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

Nimiq is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Through 1.5.0, the validity store uses a strict lower-bound comparison that expires a stored transaction too early relative to Transaction::is_valid_at, allowing a remote attacker to replay the same signed transaction during a blocks_per_batch minus one block window and cause the sender and recipient balances to be updated twice. This issue is fixed in version 1.5.1.

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%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

August 12, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Aug 26, 2026
Patch available. Sources: github_commit, github_pr, github.
github Patch Available

Validity store off by one error · Advisory · nimiq/core-rs-albatross · GitHub

https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-3763-qp59-59vf
github_pr Patch Available

Fix validity-store replay window to match transaction validity

Patch available: nimiq/core-rs-albatross v1.5.1 (PR #3772 merged 2026-05-21)

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

commit a530b2434ebc (nimiq/core-rs-albatross)

Patch available: nimiq/core-rs-albatross v1.5.1 (contains commit a530b2434ebc)

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

Vendor Advisories for CVE-2026-46369(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFixed inDependents
nimiq-blockchain—1.5.1—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 13× 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.

  1. 2026-09-19 03:14 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 02:15 UTCEG score recompute
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-17 00:22 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 10:50 UTCEG score recompute
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 06:24 UTCEG score recompute
  10. 2026-09-14 04:17 UTCEG score recompute
  11. 2026-09-13 16:47 UTCEPSS rescore
  12. 2026-09-13 03:18 UTCEG score recompute
  13. 2026-09-12 15:01 UTCEPSS rescore
  14. 2026-09-12 02:18 UTCEG score recompute
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-11 13:48 UTCEG score recompute
  17. 2026-09-11 09:37 UTCEPSS rescore
  18. 2026-09-10 09:58 UTCEG score recompute
  19. 2026-09-10 09:34 UTCEPSS rescore
  20. 2026-09-09 05:17 UTCEG score recompute
  21. 2026-09-08 22:00 UTCEPSS rescore
  22. 2026-09-07 18:24 UTCEG score recompute
  23. 2026-09-07 16:01 UTCEPSS rescore
  24. 2026-09-06 14:22 UTCEG score recompute
  25. 2026-09-06 13:47 UTCEPSS rescore
Show 19 more
  1. 2026-09-06 01:53 UTCEG score recompute
  2. 2026-09-05 00:44 UTCEG score recompute
  3. 2026-09-04 07:55 UTCEG score recompute
  4. 2026-09-04 05:06 UTCEPSS rescore
  5. 2026-09-02 23:38 UTCEG score recompute
  6. 2026-09-02 14:12 UTCEPSS rescore
  7. 2026-09-02 01:51 UTCEG score recompute
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 13:14 UTCEG score recompute
  10. 2026-08-30 22:09 UTCEG score recompute
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-30 09:40 UTCEG score recompute
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-29 08:38 UTCEG score recompute
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-27 17:24 UTCEG score recompute
  17. 2026-08-27 14:25 UTCEPSS rescore
  18. 2026-08-26 20:42 UTCEG score recompute
  19. 2026-08-12 15:21 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-46369?
CVE-2026-46369 is a high vulnerability published on August 12, 2026. Nimiq is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Through 1.5.0, the validity store uses a strict lower-bound comparison that expires a stored transaction too early relative to Transaction::isvalidat, allowing a remote attacker to replay…
When was CVE-2026-46369 disclosed?
CVE-2026-46369 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46369 actively exploited?
CVE-2026-46369 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 66.9% of all scored CVEs.
What is the CVSS score of CVE-2026-46369?
CVE-2026-46369 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-46369?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46369, 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-46369

Explore →

Is Your Infrastructure Affected by CVE-2026-46369?

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

Start Free Scan →Browse All CVEs