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

Published Jan 22, 2026
·
Updated

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 --enableretrieveapi=false.

Other sources

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 --enableretrieveapi=false.

MITRE

Affected Software

2 affected componentsFixes available
go/github.com/sigstore/rekor<=1.4.3
1.5.0
linuxfoundation Rekor<1.5.0

Event History

Jan 22, 2026
Advisory Published
via GitHub·06:41 PM
Data Sourced
via GitHub·06:41 PM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·10:05 PM
Data Sourced
via MITRE·10:05 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
RemedyAffected Software
Feb 27, 58104
Event
via FIRST·09:29 AM

Frequently Asked Questions

1

What is the severity of CVE-2026-24117?

The severity of CVE-2026-24117 is considered to be moderate due to its SSRF nature affecting internal services.

2

How do I fix CVE-2026-24117?

To fix CVE-2026-24117, update your version of the rekor package to at least 1.5.0.

3

What does CVE-2026-24117 exploit?

CVE-2026-24117 exploits a vulnerability in the /api/v1/index/retrieve endpoint that allows SSRF via user-provided URLs.

4

Which versions of rekor are affected by CVE-2026-24117?

Versions of rekor from 1.4.3 and earlier are affected by CVE-2026-24117.

5

What is SSRF in the context of CVE-2026-24117?

In the context of CVE-2026-24117, SSRF refers to Server-Side Request Forgery, allowing attackers to access internal services through crafted requests.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203