Rekor affected by Server-Side Request Forgery (SSRF) via provided public key URL
GHSA-4c4x-jm2x-pf9j · CVE-2026-24117 · GO-2026-4355
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
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.
References
- WEB https://github.com/sigstore/rekor/security/advisories/GHSA-4c4x-jm2x-pf9j
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2026-24117
- WEB https://github.com/sigstore/rekor/commit/60ef2bceba192c5bf9327d003bceea8bf1f8275f
- PACKAGE https://github.com/sigstore/rekor
- WEB https://github.com/sigstore/rekor/releases/tag/v1.5.0
Ready to move
Start Securing
Free, no credit card | First findings in minutes