Security readout for executives and security teams
Plain-English summary
CVE-2026-24117 affects Sigstore Rekor versions before 1.5.0. An unauthenticated attacker could make Rekor issue GET requests to internal services through a user-supplied public key URL. Sources state responses are not returned and state-changing requests are not possible, reducing impact to blind internal network probing.
Executive priority
Prioritize remediation for internet-facing or broadly accessible Rekor deployments. The business risk is moderate: it may help attackers map internal services, but cited sources say it cannot return internal responses or mutate state.
Technical view
The vulnerable Rekor /api/v1/index/retrieve endpoint retrieves a public key from a user-provided URL, enabling SSRF in versions 1.4.3 and below. The issue is CWE-918 with CVSS 5.3. The SSRF is limited to GET, does not expose the response to the caller, and is fixed in Rekor 1.5.0.
Likely exposure
Exposure is most relevant for organizations running Rekor before 1.5.0 with the retrieve API enabled and reachable by untrusted users or networks.
Exploitation context
The source bundle does not indicate active exploitation, and KEV is false. Exploitation would be limited to blind SSRF-style probing because responses are not returned and only GET requests are triggered.
Researcher notes
Focus validation on Rekor version, retrieve API configuration, and network reachability. Avoid assuming data exfiltration or state changes; the advisory explicitly limits impact to blind SSRF via GET. Fixed code is referenced in commit 60ef2bce and release v1.5.0.
Mitigation direction
- Upgrade Sigstore Rekor to version 1.5.0 or later.
- If upgrade is delayed, disable the retrieve API using vendor-documented --enable_retrieve_api=false.
- Restrict Rekor API exposure to trusted networks where operationally possible.
- Review vendor advisory and release notes for deployment-specific guidance.
Validation and detection
- Inventory Rekor deployments and identify versions below 1.5.0.
- Confirm whether /api/v1/index/retrieve is enabled in Rekor configuration.
- Verify Rekor API exposure from untrusted networks or users.
- Confirm upgrade to 1.5.0 or the documented workaround is applied.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-24117 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/sigstore/rekor/security/advisories/GHSA-4c4x-jm2x-pf9jCVE reference · x_refsource_CONFIRM
- https://github.com/sigstore/rekor/commit/60ef2bceba192c5bf9327d003bceea8bf1f8275fCVE reference · x_refsource_MISC
- https://github.com/sigstore/rekor/releases/tag/v1.5.0CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.