CVE-2026-54541

LOW CVSS 3.7
Published: 2026-09-14
Modified: 2026-09-14
Enriched via mock
Tenable Plugin

Checking the public Tenable catalog…

AI Threat Summary

CVE-2026-54541 is a moderate vulnerability with a CVSS score of 3.7 affecting the target software. Threat hunters should monitor for exploit attempts and apply vendor patches immediately.

Description

Nimiq is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to 1.6.0, a malicious state-sync peer can crash a syncing node by sending a crafted TrieChunk proof containing two TrieProofNode values with identical keys. TrieProof::verify calls TrieProofNode::child_index in primitives/src/trie/trie_proof_node.rs, where is_prefix_of accepts equal keys and KeyNibbles::get is called at the key length, returns None, and is unconditionally unwrapped. Untrusted ResponseChunk data reaches commit_chunks, put_chunk, and proof.verify before cryptographic proof validation, so the attacker does not need a valid proof. Exploitation requires the attacker to be selected as the victim's sync peer during state sync, and the resulting panic is transient because the node restarts and resynchronizes. This issue is fixed in version 1.6.0.

Attack Chain
1
Reconnaissance

Attacker scans for vulnerable versions using version banners or PoC scanners

2
Initial Access

Attacker triggers CVE-2026-54541 vulnerability with a crafted request or payload

3
Execution

Vulnerability exploited to perform unauthorized actions on the target system

4
Impact

Depending on vulnerability type, attacker achieves data access, service disruption, or code execution

MITRE ATT&CK Techniques
T1190 Exploit Public-Facing Application
Initial Access

Public-facing application vulnerability exploited for initial access

T1203 Exploitation for Client Execution
Execution

Vulnerability exploited to execute attacker-controlled code

Indicators of Compromise
Type Value Description
user_agent Mozilla/5.0 (compatible; exploit/1.0) Generic exploit scanner user agent pattern
url /api/vuln-endpoint?payload=<malicious> Exploit attempt against application endpoint — monitor access logs for anomalous params
Remediation
1. Apply vendor-supplied security patches immediately. 2. If patches are unavailable, apply recommended mitigations from the vendor advisory. 3. Enable WAF rules or IDS signatures to detect exploitation attempts. 4. Monitor logs for indicators of compromise listed above. 5. Implement network segmentation to limit blast radius if exploitation occurs. 6. Subscribe to vendor security advisories for this product.