Description
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.
Published: 2026-06-01
Score: 5.8 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A flaw in Clair’s fetcher allows outbound HTTP requests to attacker-supplied URIs from manifest layer descriptors without filtering the IP address or scheme. When a pre‑shared key (PSK) is not configured, an unauthenticated attacker can submit a manifest that targets internal services or cloud metadata endpoints. The response is reflective: non‑200 responses leak up to 256 bytes of the error body through CheckResponse error messages. The weakness is a classic Server Side Request Forgery (CWE‑918), giving an attacker the ability to probe internal network resources.

Affected Systems

The vulnerability exists in Red Hat Quay 3 when it is deployed without PSK authentication. Operator‑managed Quay deployments typically enable PSK by default, which eliminates the unauthenticated attack vector. Unmanaged or custom Quay installations that do not enable PSK remain susceptible.

Risk and Exploitability

The CVSS score of 5.8 indicates a medium severity. EPSS data are not available, and the vulnerability is not listed in CISA KEV. Exploitation requires access to the Quay API to submit a crafted manifest, so while the vector is unprivileged, the attacker must have network reach to the Quay service. The reflective leakage provides a limited but consistent window for internal reconnaissance.

Generated by OpenCVE AI on June 1, 2026 at 10:25 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Ensure that pre‑shared key authentication is enabled on the Quay instance to protect the fetcher component from unauthenticated access.
  • Configure the Quay manifest processing settings to restrict or whitelist URIs so that only trusted networks or trusted registries are requested.
  • Apply the latest Clair update or patch that removes the unfiltered URI handling; if a patch is not available, temporarily disable the ability to submit external manifest layer URIs through configuration.

Generated by OpenCVE AI on June 1, 2026 at 10:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-698x-9w2p-7vvp Claircore: Unauthenticated attackers can submit manifests with URIs pointing to internal services or cloud metadata endpoints
History

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

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


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 cpe:/a:redhat:quay:3
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

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


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

{'score': 5.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N'}


cve-icon MITRE

Status: REJECTED

Assigner: redhat

Published:

Updated: 2026-07-27T08:35:41.456Z

Reserved: 2026-06-01T07:25:15.700Z

Link: CVE-2026-10517

cve-icon Vulnrichment

Updated:

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-06-01T09:16:16.447

Modified: 2026-06-01T16:57:45.130

Link: CVE-2026-10517

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-02T20:15:16Z

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)