nimiq core-rs-albatross up to 1.2.x put_historic_txns assertion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 2.13 |
Summary
A vulnerability was found in nimiq core-rs-albatross up to 1.2.x. It has been declared as problematic. Affected is the function HistoryStore::put_historic_txns. Executing a manipulation can lead to assertion.
This vulnerability is registered as CVE-2026-34066. It is possible to launch the attack remotely. No exploit is available.
It is recommended to upgrade the affected component.
Details
A vulnerability has been found in nimiq core-rs-albatross up to 1.2.x and classified as problematic. This vulnerability affects the function HistoryStore::put_historic_txns. The manipulation with an unknown input leads to a assertion vulnerability. The CWE definition for the vulnerability is CWE-617. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. As an impact it is known to affect availability. CVE summarizes:
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.
The advisory is available at github.com. This vulnerability was named CVE-2026-34066 since 03/25/2026. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit.
Upgrading to version 1.3.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 6f5511309c199d84b012fe6b9aba7e5582892c50 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.2VulDB Meta Temp Score: 4.1
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.3
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AssertionCWE: CWE-617
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: core-rs-albatross 1.3.0
Patch: 6f5511309c199d84b012fe6b9aba7e5582892c50
Timeline
03/25/2026 CVE reserved04/22/2026 Advisory disclosed
04/22/2026 VulDB entry created
04/22/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-j99g-7rqw-q9jg
Status: Confirmed
CVE: CVE-2026-34066 (🔒)
GCVE (CVE): GCVE-0-2026-34066
GCVE (VulDB): GCVE-100-359050
Entry
Created: 04/22/2026 22:27Changes: 04/22/2026 22:27 (67)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.