GHSA-4c4x-jm2x-pf9j

    Dashboard / Vulnerabilities / GHSA-4c4x-jm2x-pf9j

    GHSA-4c4x-jm2x-pf9j

    Published: 22 Jan 2026Last Modified: 10 Sept 2026

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

    Details: ## 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](https://portswigger.net/web-security/ssrf/blind). ## 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`.

    Affected packages

    Package

    Name: github.com/sigstore/rekor

    Purl: pkg:golang/github.com/sigstore/rekor

    Affected ranges

    Type: SEMVER

    Events:

    Introduced- 0
    Fixed -1.5.0

    Affected versions

    Common Vulnerability Scoring System

    Attack Vector
    Network
    Adjacent
    Local
    Physical
    Privileges Required
    None
    Low
    High
    User Interaction
    None
    Required
    Scope
    Unchanged
    Changed
    Confidentiality
    None
    Low
    High
    Integrity
    None
    Low
    High
    Availability
    None
    Low
    High
    GHSA-4c4x-jm2x-pf9j | CVE-DB