github.com/sigstore/rekor

CVE-2026-23831

CVE-2026-23831 is a medium-severity null pointer dereference vulnerability in github.com/sigstore/rekor (go), affecting versions <= 1.4.3. It is fixed in 1.5.0.

Key facts
CVSS score
5.3
Medium
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
github.com/sigstore/rekor
Fixed in
1.5.0
Disclosed
2026

Summary

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

Impact

What is null pointer dereference?

The application dereferences a null pointer, causing a crash. Typical impact: denial of service via crash.

Severity and exposure

CVE-2026-23831 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (1.5.0). Upgrading removes the vulnerable code path.

Affected versions

go

  • github.com/sigstore/rekor (<= 1.4.3)

Security releases

  • github.com/sigstore/rekor → 1.5.0 (go)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-23831 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-23831 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2026-23831 in your environment

Remediation advice

Upgrade github.com/sigstore/rekor to 1.5.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-23831

What is CVE-2026-23831?

CVE-2026-23831 is a medium-severity null pointer dereference vulnerability in github.com/sigstore/rekor (go), affecting versions <= 1.4.3. It is fixed in 1.5.0. The application dereferences a null pointer, causing a crash.

How severe is CVE-2026-23831?

CVE-2026-23831 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/sigstore/rekor are affected by CVE-2026-23831?

github.com/sigstore/rekor (go) versions <= 1.4.3 is affected.

Is there a fix for CVE-2026-23831?

Yes. CVE-2026-23831 is fixed in 1.5.0. Upgrade to this version or later.

Is CVE-2026-23831 exploitable, and should I be worried?

Whether CVE-2026-23831 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-23831 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-23831?

Upgrade github.com/sigstore/rekor to 1.5.0 or later.

Stop the waste.
Protect your environment with Kodem.