VulnerabilityAnalyzed

CVE-2026-24117

In versions 1.4.3 and below, attackers can trigger SSRF to arbitrary internal services because /api/v1/index/retrieve supports retrieving a public key via user-provided URL.

MEDIUM 5.3EPSS 0.34%

Does this matter?

Lower severity and a low EPSS score (0.34%). Track it; it rarely justifies an emergency change on its own.

Description

Rekor is a software supply chain transparency log. In versions 1.4.3 and below, attackers can trigger SSRF to arbitrary internal services because /api/v1/index/retrieve supports retrieving a public key via user-provided URL. Since the SSRF only can trigger GET requests, the request cannot mutate state. The response from the GET request is not returned to the caller so data exfiltration is not possible. A malicious actor could attempt to probe an internal network through Blind SSRF. The issue has been fixed in version 1.5.0. To workaround this issue, disable the search endpoint with --enable_retrieve_api=false.

CVSS 3.1: 5.3 MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS: 0.34% probability · 28th percentile
CISA KEV: Not listed
Weakness: CWE-918
Affected: linuxfoundation/rekor
Source: security-advisories@github.com

References

https://github.com/sigstore/rekor/commit/60ef2bceba192c5bf9327d003bceea8bf1f8275fPatch
https://github.com/sigstore/rekor/releases/tag/v1.5.0Product, Release Notes
https://github.com/sigstore/rekor/security/advisories/GHSA-4c4x-jm2x-pf9jVendor Advisory

Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.