Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-698x-9w2p-7vvp | Claircore: Unauthenticated attackers can submit manifests with URIs pointing to internal services or cloud metadata endpoints |
| Link | Providers |
|---|---|
| https://access.redhat.com/security/cve/CVE-2026-10517 |
|
Mon, 27 Jul 2026 09:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Clair: clair: unauthenticated ssrf via manifest layer uri enables internal network reconnaissance | |
| Metrics |
ssvc
|
Mon, 27 Jul 2026 09:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in Clair. The fetcher component makes outbound HTTP requests to attacker-supplied URIs from manifest layer descriptors without IP or scheme filtering. When PSK authentication is not configured (opt-in, not enforced by default), an unauthenticated attacker can submit a manifest with a URI pointing to internal services or cloud metadata endpoints. The SSRF is reflective for non-200 responses, leaking up to 256 bytes of error body content via CheckResponse error messages. Operator-managed Red Hat Quay deployments auto-configure PSK and are not exposed to the unauthenticated attack vector. | 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. |
| CPEs | ||
| References |
|
Thu, 25 Jun 2026 23:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Mon, 01 Jun 2026 11:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 01 Jun 2026 09:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in Clair. The fetcher component makes outbound HTTP requests to attacker-supplied URIs from manifest layer descriptors without IP or scheme filtering. When PSK authentication is not configured (opt-in, not enforced by default), an unauthenticated attacker can submit a manifest with a URI pointing to internal services or cloud metadata endpoints. The SSRF is reflective for non-200 responses, leaking up to 256 bytes of error body content via CheckResponse error messages. Operator-managed Red Hat Quay deployments auto-configure PSK and are not exposed to the unauthenticated attack vector. | |
| Title | Clair: clair: unauthenticated ssrf via manifest layer uri enables internal network reconnaissance | |
| First Time appeared |
Redhat
Redhat quay |
|
| Weaknesses | CWE-918 | |
| CPEs | cpe:/a:redhat:quay:3 | |
| Vendors & Products |
Redhat
Redhat quay |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: REJECTED
Assigner: redhat
Published:
Updated: 2026-07-27T08:35:41.456Z
Reserved: 2026-06-01T07:25:15.700Z
Link: CVE-2026-10517
Updated:
Status : Awaiting Analysis
Published: 2026-06-01T09:16:16.447
Modified: 2026-06-01T16:57:45.130
Link: CVE-2026-10517
No data.
OpenCVE Enrichment
Updated: 2026-06-02T20:15:16Z
-
CWE-918
Server-Side Request Forgery (SSRF)
Github GHSA