GitHub Advisoryadvisory · Go

GHSA-4c4x-jm2x-pf9j Rekor affected by Server-Side Request Forgery (SSRF) via provided public key URL

MEDIUM Published 2026-01-22 Modified 2026-01-23 Official page ↗
Aliases
CVE-2026-24117
Ecosystem
Go
Packages
github.com/sigstore/rekor
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Weaknesses
CWE-918
Reviewed
2026-01-22

Affected packages

• Go github.com/sigstore/rekor: < 1.5.0 → fixed in 1.5.0

Description

Summary `/api/v1/index/retrieve` supports retrieving a public key via a user-provided URL, allowing attackers to trigger SSRF to arbitrary internal services. 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. Impact • SSRF to cloud metadata (169.254.169.254) • SSRF to internal Kubernetes APIs • SSRF to any service accessible from Fulcio's network Patches Upgrade to v1.5.0. Note that this is a breaking change to the search API and fully disables lookups by URL. If you require this feature, please reach out and we can discuss alternatives. Workarounds Disable the search endpoint with `--enable_retrieve_api=false`.

Related

Alias · CVE (1)

  • CVE-2026-24117 Rekor is a software supply chain transparency log. vulnerability

Weakness · CWE (1)

  • CWE-918 Server-Side Request Forgery weakness

References