1sealsemantic last-mile verification

Research / Finding

Panic in history index request handlers when a full node runs without the history index

F-NIMIQ-HISTORYINDEX-PANIC-001

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Read the evidence · View in research browse

Recorded evidence

5.3medium
CVE-2026-35468CVEnimiq/core-rs-albatross

Panic in history index request handlers when a full node runs without the history index

Fixed in: nimiq-blockchain v1.3.0

patched
details
Finding IDs
F-NIMIQ-HISTORYINDEX-PANIC-001
CVE
CVE-2026-35468
GHSA
GHSA-xr78-2jhh-9wf9
Status
patched
Fixed in
nimiq-blockchain v1.3.0
Recorded credit
finder: @1seal
Note
GHSA-xr78-2jhh-9wf9; patched in v1.3.0 via PR #3667
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
CVE registry state
PUBLISHED
CVE state checked
Upstream title
Panic in history index request handlers when a full node runs without the history index
Upstream CWE
CWE-252
Upstream publication
Upstream updated
Metadata fetched
Upstream @1seal credit
@1seal: finder (accepted)

F-NIMIQ-HISTORYINDEX-PANIC-001: Input / state handling. History index input reaches a panic. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-NIMIQ-HISTORYINDEX-PANIC-001

Security area (1seal assessment): Availability. History index input reaches a panic. Reviewed 24 Sep 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.