Advisory record · GHSA-4c4x-jm2x-pf9j

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

CVSS 5.3 MediumEPSS 0.0036 · 30th percentile

Published by the GitHub Advisory Database at 22 Jan 2026, 18:41 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/sigstore/rekorGo<1.5.01.5.0
Identifiers
GHSA-4c4x-jm2x-pf9j · CVE-2026-24117 · GO-2026-4355
Weakness (CWE)
CWE-918
Published
22 Jan 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Rekor versions before 1.5.0 are vulnerable to server-side request forgery through the /api/v1/index/retrieve endpoint, which can fetch a public key from a user-supplied URL. An attacker with access to that endpoint can make the server send GET requests to arbitrary internal services, but the responses are not returned, so this is blind probing only. Upgrade to Rekor 1.5.0, which removes lookup by URL; alternatively, disable the search endpoint with the enable_retrieve_api=false setting.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0036, the 30th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:13 UTC First seen by agentprime
  2. 31 Oct 2026, 14:13 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.