CVE-2026-10517: Claircore Unauthenticated Attackers Can Submit Manifests Vulnerability

MODERATE
Advisory Identifier: GHSA-698x-9w2p-7vvp
Share
CVSS 5.8
CWE-918
Published
Advisory Summary

CVE-2026-10517 is a MODERATE (CVSS 5.8) unauthenticated attackers can submit manifests vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting Claircore libraries in the Go ecosystem. The issue involves unauthenticated attackers can submit manifests with uris pointing to internal services or cloud metadata endpoints. Remediation is available in the latest vendor maintenance releases.

CVE-2026-10517 at a Glance

CVE Identifier CVE-2026-10517
GHSA Identifier GHSA-698x-9w2p-7vvp
Severity MODERATE
CVSS v3.1 Base Score 5.8
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product Claircore
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 5.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-10517

To remediate this vulnerability, upgrade all affected Claircore dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/quay/claircore fixed: Latest secure release 
Upgrade github.com/quay/claircore to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for github.com/quay/claircore

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-10517, inspect your project dependencies for Claircore:

inspect dependencies for github.com/quay/claircore

Analyze the terminal output to locate any version of Claircore in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In Claircore, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

CVE-2026-10517 Affected Claircore Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
github.com/quay/claircore
golang/github.com/quay/claircore
Go
≤ 1.5.52

References

NVD — CVE-2026-10517 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-10517
Claircore Security Information SECURITY
https://access.redhat.com/security/cve/CVE-2026-10517
bugzilla.redhat.com/show_bug.cgi WEB
https://bugzilla.redhat.com/show_bug.cgi?id=2486779
Claircore Source Repository REPOSITORY
https://github.com/quay/claircore

Frequently Asked Questions

What is CVE-2026-10517?
CVE-2026-10517 is a security vulnerability in Claircore involving Unauthenticated attackers can submit manifests with URIs pointing to internal services or cloud metadata endpoints under CWE-918: Server-Side Request Forgery (SSRF).
Which Claircore versions are affected?
Affected versions include releases prior to current release patches across affected packages: github.com/quay/claircore.
What version fixes CVE-2026-10517?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/quay/claircore affected?
Yes, github.com/quay/claircore is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2026-10517?
CVE-2026-10517 has a CVSS v3.1 base score of 5.8 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N.
What CWE is associated with CVE-2026-10517?
CVE-2026-10517 is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check Go dependencies for CVE-2026-10517?
Run the dependency tree command: 'inspect dependencies for github.com/quay/claircore'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-698x-9w2p-7vvp",
  "modified" : "2026-07-07T23:47:00Z",
  "published" : "2026-06-01T09:31:12Z",
  "aliases" : [ "CVE-2026-10517" ],
  "summary" : "Claircore: Unauthenticated attackers can submit manifests with URIs pointing to internal services or cloud metadata endpoints",
  "details" : "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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/quay/claircore"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "1.5.52"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-10517"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/security/cve/CVE-2026-10517"
  }, {
    "type" : "WEB",
    "url" : "https://bugzilla.redhat.com/show_bug.cgi?id=2486779"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/quay/claircore"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-07T23:47:00Z",
    "nvd_published_at" : "2026-06-01T09:16:16Z"
  }
}