NULL Pointer Dereference Affecting ratify-fips package, versions <1.4.0-r11


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.04% (14th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about NULL Pointer Dereference vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CHAINGUARDLATEST-RATIFYFIPS-15228226
  • published5 Feb 2026
  • disclosed22 Jan 2026

Introduced: 22 Jan 2026

NewCVE-2026-23831  (opens in a new tab)
CWE-476  (opens in a new tab)

How to fix?

Upgrade Chainguard ratify-fips to version 1.4.0-r11 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream ratify-fips package and not the ratify-fips package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1