CVE-2026-10517 Details
Description
Rejected reason: Retracted following review by Red Hat Product Security and confirmation from the upstream Clair/Claircore maintainer. This CVE misattributes the described behavior to github.com/quay/claircore: the authentication mechanism in question (optional PSK, HTTP endpoint /indexer/api/v1/index_report) is implemented entirely in github.com/quay/clair; no PSK-related code exists anywhere in claircore's codebase or git history. The unauthenticated indexer API is Clair's documented, intentional design, authentication is an opt-in deployment choice, not a code defect. No fix commit was found in claircore between the version recorded as the affected boundary (1.5.52) and the following release (1.5.53); intervening commits are unrelated dependency and feature changes, so the "fixed in 1.5.52" status is inaccurate.
A server-side request forgery (SSRF) vulnerability has been identified in Clair's fetcher component. This issue arises because the fetcher makes outbound HTTP requests to attacker-supplied URIs from manifest layer descriptors without filtering IP addresses or schemes. When pre-shared key (PSK) authentication is not enabled—an opt-in feature not enforced by default—an unauthenticated attacker can submit a manifest with a URI that points to internal services or cloud metadata endpoints. The SSRF is reflective for non-200 responses, leaking up to 256 bytes of error body content through CheckResponse error messages. While operator-managed Red Hat Quay deployments automatically configure PSK and are not vulnerable to this unauthenticated attack vector, standalone Clair deployments without PSK configuration are exposed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No CVSS 3.x data is available for this CVE.
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
No references are available for this CVE.
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
No affected product data is available for this CVE.
Change History
7 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 27, 2026 | CVE Rejected | [email protected] |
| Jul 27, 2026 | CVE Modified | [email protected] |
| Jul 22, 2026 | CVE Translated | [email protected] |
| Jun 26, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jun 1, 2026 | New CVE Received | [email protected] |