Rekor is a software supply chain transparency log. In versions 1.4.3 and below, the entry implementation can…
Historical advisory recorded 25 Oct 2026 05:17:36 UTC. Read the latest advisory.
nvd · CVE-2026-23831
PublishedRekor 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 with an empty spec.message, causing nil Pointer Dereference. Function validate() returns nil (success) when message is empty, leaving sign1Msg uninitialized, and Canonicalize() later dereferences v.sign1Msg.Payload. 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. This issue has been fixed in version 1.5.0.
Read the publisher's advisoryAffected versions, risk and source history
nvd · CVE-2026-23831
PublishedNVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-476
Original publisher date fields
published: 2026-01-22T22:16:19.523
lastModified: 2026-06-17T10:22:10.360
1 source CPE criteria · context only
- cpe:2.3:a:linuxfoundation:rekor:*:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON