What’s Vulnerable › Vulnerabilities
CVE-2026-24117: Rekor affected by Server-Side Request Forgery (SSRF) via provided public key URL
- Severity: medium (CVSS 5.3 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.4% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-01-22 · updated 2026-06-17
- Weakness: CWE-918
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 products
- sigstore rekor: before 1.5.0 — fixed in 1.5.0
How to fix
Upgrade to a fixed version: sigstore rekor 1.5.0. Check the vendor advisory for mitigations.
References
- https://github.com/sigstore/rekor/commit/60ef2bceba192c5bf9327d003bceea8bf1f8275f
- https://github.com/sigstore/rekor/releases/tag/v1.5.0
- https://github.com/sigstore/rekor/security/advisories/GHSA-4c4x-jm2x-pf9j
Get alerted when CVE-2026-24117 or the next vulnerability affects your stack