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

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

F-REKOR-SSRF-001

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Recorded evidence

5.3medium

CVE-2026-24117CVEsigstore/rekor

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

Fixed in: rekor 1.5.0

patched

details

Finding IDs: F-REKOR-SSRF-001
CVE: CVE-2026-24117
GHSA: GHSA-4c4x-jm2x-pf9j
Status: patched
Fixed in: rekor 1.5.0
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CVE registry state: PUBLISHED
CVE state checked: 23 Sep 2026
Upstream title: Server-Side Request Forgery (SSRF) via provided public key URL
Upstream CWE: CWE-918
Upstream publication: 22 Jan 2026
Upstream updated: 22 Jan 2026
Metadata fetched: 23 Sep 2026
Upstream @1seal credit: @1seal: reporter (accepted)

F-REKOR-SSRF-001: Outbound request trust. The public-key URL controls an outbound request destination. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-REKOR-SSRF-001

Security area (1seal assessment): Authorization. The public-key URL controls an outbound request destination. Reviewed 24 Sep 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.