Is CVE-2026-10517 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-10517 being exploited in the wild.

How severe is CVE-2026-10517?

Medium severity, with a CVSS score of 5.8, published 1 June 2026.

Which products and versions are affected?

github.com/quay/claircore (Go) <= 1.5.52, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.5.52; Quay Claircore <= 1.5.52; Red Hat Clair <= 1.5.52.

Is there a fix for CVE-2026-10517?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-10517 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-10517?

Check whether you run github.com/quay/claircore (Go), Quay Claircore or Red Hat Clair at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-10517: Red Hat Clair SSRF in fetcher component

Q: Is there a fix for CVE-2026-10517?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2026-10517 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-10517?

Check whether you run github.com/quay/claircore (Go), Quay Claircore or Red Hat Clair at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-10517 · Severity: medium · CVSS 5.8 · Published 2026-06-01

Clair, a tool used for scanning container images for security vulnerabilities, contains a flaw that allows attackers to trick the system into making unauthorized network requests. If the software is not configured with specific security keys, an unauthenticated attacker can use this to probe internal corporate networks or access sensitive cloud metadata. This could lead to the exposure of internal service details or small amounts of sensitive configuration data.

Technologies: Quay Claircore. Vendors: Go, Quay, Red Hat.

Quick answers

Is CVE-2026-10517 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-10517 being exploited in the wild.
How severe is CVE-2026-10517?: Medium severity, with a CVSS score of 5.8, published 1 June 2026.
Which products and versions are affected?: github.com/quay/claircore (Go) <= 1.5.52, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.5.52; Quay Claircore <= 1.5.52; Red Hat Clair <= 1.5.52.
Is there a fix for CVE-2026-10517?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-10517 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-10517?: Check whether you run github.com/quay/claircore (Go), Quay Claircore or Red Hat Clair at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in the Claircore fetcher component. The component fails to perform IP or scheme filtering on attacker-supplied URIs within manifest layer descriptors. In deployments where Pre-Shared Key (PSK) authentication is not explicitly configured, an unauthenticated attacker can submit a manifest pointing to internal services or cloud metadata endpoints (e.g., 169.254.169.254). While full response exfiltration is prevented by digest validation, the vulnerability is reflective; the 'CheckResponse' function leaks up to 256 bytes of error body content from non-200 responses, along with Content-Type headers and redirect URLs. Operator-managed Red Hat Quay deployments are generally protected as they auto-configure PSK by default.

Affected products

Quay Claircore <= 1.5.52
Red Hat Clair 3

Identifiers

CVE-2026-10517
GHSA-698x-9w2p-7vvp
GO-2026-5939

Timeline

2026-06-01: disclosed: Initial disclosure and NVD publication
2026-06-01: advisory: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.