Rekor's COSE v0.0.1 entry type nil pointer dereference in Canonicalize via empty Message
## Summary Rekor’s cose v0.0.1 entry implementation can panic on attacker-controlled input when canonicalizing a proposed entry with an empty `spec.message`. `validate()` returns nil (success) when `message` is empty, leaving `sign1Msg` uninitialized, and `Canonicalize()` later dereferences `v.sign1Msg.Payload`. ## Impact A malformed proposed entry of the `cose/v0.0.1` type can cause a panic on a thread within the Rekor process. The thread is recovered so the client receives a 500 error message and service still continues, so the availability impact of this is minimal. ## Patches Upgrade to v1.5.0 ## Workarounds None
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-23831US | — | — | ||
Rekor is a software supply chain transparency log. In versions 1.4.3 and below, the entry implementation can panic on attacker-controlled input when canonicalizing a proposed entry… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/sigstore/rekorPACKAGE
- https://github.com/sigstore/rekor/commit/39bae3d192bce48ef4ef2cbd1788fb5770fee8cdWEB
- https://github.com/sigstore/rekor/releases/tag/v1.5.0WEB
- https://github.com/sigstore/rekor/security/advisories/GHSA-273p-m2cw-6833WEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-23831ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan