What is the CVSS score of CVE-2026-35468?

CVE-2026-35468 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. EPSS exploitation probability: 0.0%.

Core Rs Albatross CVE-2026-35468

HIGH

Unchecked Return Value (CWE-252)

2026-04-03 GitHub_M

Information Disclosure Core Rs Albatross Nimiq

7.5

CVSS 3.1 · NVD

View

Vulnerability Assessment

Weakness	CWE CWE-252 OWASP Top 10:2025 A10:2025 - Mishandling of Exceptional Conditions ASVS 5.0 V16 - Security Logging and Error Handling Return value checking
Impact	The CVSS score of 5.3 with attack vector network and low complexity reflects a straightforward remote denial of service with no authentication required. However, the real-world impact is context-dependent: the vulnerability only affects nodes in specific operational states (syncing or intentionally running without history indexing), not all deployments. The EPSS exploitation probability is not provided, but the presence of an upstream fix commit and GitHub security advisory indicates the vulnerability is understood and remediated. The attack requires neither authentication nor user interaction, and network-accessible Nimiq full nodes are theoretically targetable by any peer. The practical risk tier depends on node operator awareness and upgrade velocity; nodes in active sync or minimal-resource configurations face elevated risk, while fully indexed nodes are unaffected by the faulty code path. The availability impact is complete for affected nodes (crash/restart), but no confidentiality or integrity breach is possible.
Exploit ScenarioDerived	A remote attacker connected to a Nimiq full node that is actively syncing or running without a history index sends a crafted RequestTransactionsProof or RequestTransactionReceiptsByAddress peer message to the node's consensus request handler. The handler invokes history_index().unwrap() on the HistoryStoreProxy, which returns None for the valid WithoutIndex state, triggering a Rust panic and crashing the node. The attacker can repeat this process to maintain denial of service by repeatedly crashing and recovering nodes in vulnerable configurations.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 03, 2026

Denial of service in Nimiq Core RS Albatross prior to version 1.3.0 allows remote attackers to crash full nodes by sending specially crafted consensus requests (RequestTransactionsProof or RequestTransactionReceiptsByAddress) when the node is operating without a history index. The vulnerability stems from unsafe unwrap() calls that panic when encountering a valid but unindexed state, affecting nodes during synchronization or when intentionally configured without history indexing.

RemediationAI

Upgrade Nimiq Core RS Albatross to version 1.3.0 or later. The vendor-released patch version 1.3.0 resolves the unsafe unwrap() calls by properly handling the None case when the history index is unavailable. Node operators should prioritize this upgrade, particularly those running nodes in sync mode or with intentionally disabled history indexing. The fix is available via the official Nimiq GitHub repository at https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0 and the upstream commit at https://github.com/nimiq/core-rs-albatross/commit/0e5c90a6c75b722f3d6091769776a4040e694dba.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Nimiq Core RS Albatross is a Rust implementation of the Nimiq Proof-of-Stake blockchain protocol using the Albatross consensus algorithm. The vulnerability exists in two peer-facing consensus request handlers that invoke blockchain.history_store.history_index().unwrap() without first validating whether the history index is available. The HistoryStoreProxy enum explicitly defines a WithoutIndex state that returns None from history_index(), a valid operational configuration for nodes syncing or running with reduced resources. The root cause is CWE-252 (Unchecked Return Value), where the code assumes a successful return without handling the None variant. This panic-based denial of service occurs at the network protocol layer when remote peers interact with the node's request handling mechanism.

Know when Core Rs Albatross gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

Severity Changed

Jul 24, 2026 - 21:22 NVD

MEDIUM HIGH

CVSS changed

Jul 24, 2026 - 21:22 NVD

5.3 (MEDIUM) 7.5 (HIGH)

CVE Published

Apr 03, 2026 - 22:10 nvd

MEDIUM 5.3

DescriptionNVD

nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, two peer-facing consensus request handlers assume that the history index is always available and call blockchain.history_store.history_index().unwrap() directly. That assumption is false by construction. HistoryStoreProxy::history_index() explicitly returns None for the valid HistoryStoreProxy::WithoutIndex state. when a full node is syncing or otherwise running without the history index, a remote peer can send RequestTransactionsProof or RequestTransactionReceiptsByAddress and trigger an Option::unwrap() panic on the request path. This issue has been patched in version 1.3.0.

Threat Intelligence Overview

EPSS Score

0.0%

Top 88% exploitable

Social Media

Sightings

Data Quality

6 sources

Confidence: High

NVD

CVE.org

EPSS

Vulnrichment CIRCL

GitHub

VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC No

EPSS 0.0%

Patch available No

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Scheduled

Exploitation

None

System Exposure· derived

Open

Automatable

Yes

Human Impact· derived

Medium

Technical Impact

Partial

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +38

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.