Rekor's COSE v0.0.1 entry type nil pointer dereference in Canonicalize via empty Message

TRUNG BÌNH 5.3CVE-2026-23831 · GHSA-273p-m2cw-6833 · GO-2026-4354 · Công bố 22/01/2026 · cập nhật 17/06/2026

Tóm tắt nhanh

CVE-2026-23831 là lỗ hổng mức TRUNG BÌNH (CVSS 5.3) ảnh hưởng github.com/sigstore/rekor, rekor (linuxfoundation).
Xác suất bị khai thác trong 30 ngày tới (EPSS): 0.43%, cao hơn 36.9% các lỗ hổng khác.
Cách xử lý: cập nhật lên 1.5.0 hoặc mới hơn.

Gói / sản phẩm	Phiên bản bị ảnh hưởng	Phiên bản đã vá
github.com/sigstore/rekor Go	`< 1.5.0`	`1.5.0`
rekor linuxfoundation	`< 1.5.0`	`1.5.0`

Mô tả

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

Mô tả của NVD

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 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.