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

> Attackers can perform blind SSRF to probe internal networks via the public key retrieval endpoint in Rekor.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jan 2026
- **Updated:** 23 Jan 2026
- **Also known as:** AZL-76446, AZL-76542, AZL-76547, AZL-76608, CLEANSTART-2026-CM50083, CLEANSTART-2026-WK71465, DEBIAN-CVE-2026-24117, GHSA-4c4x-jm2x-pf9j, GO-2026-4355, MINI-3j7j-6r9h-39w2, MINI-9h3w-7g89-64vj, MINI-cw67-wpmc-mwvm, MINI-fvqc-4hh9-f6gc, MINI-ghjq-836v-3j44, MINI-gvwq-8x32-7q4h, MINI-gwfv-vm8c-m586, MINI-h73c-rpgh-m6jc, MINI-hp3j-h2vh-mrgh, MINI-j52j-9rf3-89r3, MINI-j6mj-3fv3-w85v, MINI-jcxc-2j8x-g5qg, MINI-jr72-x3xm-mv35, MINI-p22v-gm8r-8342, MINI-p964-h77h-wxxp, MINI-pq6q-hf2w-m2p8, MINI-qjcc-jq5g-3rqx, MINI-rf37-22wc-pwhh, MINI-rv99-wprj-pv4h, MINI-v77x-m7cx-v5c3, MINI-w438-gf4r-rr27, MINI-w88v-795h-h3wc, MINI-xmhw-vgcv-wq6r, UBUNTU-CVE-2026-24117

## What is CVE-2026-24117?

CVE-2026-24117 is a medium-severity server-side request forgery vulnerability in sigstore rekor, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-24117?

3 open source packages ship an affected version, including github.com/sigstore/rekor. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/sigstore/rekor` | Go | All versions | 1.5.0 |
| `github.com/sigstore/rekor` | Go | All versions | 1.5.0 |
| `github.com/sigstore/rekor` | Go | All versions | 1.5.0 |

Products: Linuxfoundation Rekor.

## How do I fix CVE-2026-24117?

Upgrade github.com/sigstore/rekor to 1.5.0 or later.

## Is CVE-2026-24117 being exploited?

There is no known exploitation of CVE-2026-24117 in the wild and no public exploit code.

## Other vulnerabilities in sigstore rekor

- [CVE-2023-30551](https://insights.sbomify.com/CVE-2023-30551/): Rekor's compressed archives can result in OOM conditions (high 7.5)
- [CVE-2026-23831](https://insights.sbomify.com/CVE-2026-23831/): Rekor COSE v0.0.1 Canonicalize crashes when passed empty Message (medium 5.3)
- [CVE-2023-33199](https://insights.sbomify.com/CVE-2023-33199/): malformed proposed intoto v0.0.2 entries can cause a panic in Rekor (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24117 and fix it if it is affected.

What it is: CVE-2026-24117 is a medium-severity server-side request forgery vulnerability in sigstore rekor, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-24117 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/sigstore/rekor (Go): affected all versions; fixed in 1.5.0
- github.com/sigstore/rekor (Go): affected all versions; fixed in 1.5.0
- github.com/sigstore/rekor (Go): affected all versions; fixed in 1.5.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24117/ (Markdown: https://insights.sbomify.com/CVE-2026-24117/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24117
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24117
- OSV: https://osv.dev/vulnerability/CVE-2026-24117

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24117/
Summaries are generated and may contain mistakes; the official description above is the record.