Vulnerability · Published Jan 22, 2026 · Assigned by GitHub_M

CVE-2026-24117Rekor affected by Server-Side Request Forgery (SSRF) via provided public key URL

Medium 5.3

In plain English

A medium-severity server-side request forgery in rekor from sigstore. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 30% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)5.3Medium
Exploit odds (30 days)0.4%top 69.7% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

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

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:13rekorno fix listedDEBIAN-CVE-2026-24117
Debian:14rekor1.5.0-1DEBIAN-CVE-2026-24117
Gogithub.com/sigstore/rekor1.5.0GHSA-4c4x-jm2x-pf9j
Gogithub.com/sigstore/rekor1.5.0GO-2026-4355
Ubuntu:25.10rekorno fix listedUBUNTU-CVE-2026-24117
Ubuntu:26.10rekorno fix listedUBUNTU-CVE-2026-24117

Affected products (as reported)

VendorProductVersions
sigstore rekor < 1.5.0

Weakness: CWE-918 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

References