1sealsemantic last-mile verification

Research / Finding

Peer-triggerable panic during history sync

F-NIMIQ-HISTORYSYNC-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-34066CVEnimiq/core-rs-albatross

Peer-triggerable panic during history sync

Fixed in: v1.3.0

patched
details
Finding IDs
F-NIMIQ-HISTORYSYNC-PANIC-001
CVE
CVE-2026-34066
GHSA
GHSA-j99g-7rqw-q9jg
Status
patched
Fixed in
v1.3.0
Recorded credit
finder: @1seal
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H
CVE registry state
PUBLISHED
CVE state checked
Upstream title
Peer-triggerable panic during history sync
Upstream CWE
CWE-20, CWE-617, CWE-754
Upstream publication
Upstream updated
Metadata fetched
Upstream @1seal credit
@1seal: finder (accepted)

F-NIMIQ-HISTORYSYNC-PANIC-001: Input / state handling. History synchronization input violates parser state assumptions. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

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

Security area (1seal assessment): Availability. History synchronization input violates parser state assumptions. 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.