dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-10517

MEDIUM · 5.8 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Clair's fetcher component processes manifest layer descriptors and makes outbound HTTP requests to attacker-supplied URIs without IP address or scheme validation. When PSK (Pre-Shared Key) authentication is not configured (opt-in, not default), unauthenticated attackers can submit manifests with URIs pointing to internal services or cloud metadata endpoints, enabling reflective SSRF that leaks up to 256 bytes of error body content via CheckResponse messages.

MitigationEnable and configure PSK authentication for Clair to block unauthenticated manifest submissions. Consider implementing network-level filtering to restrict the fetcher's outbound HTTP capabilities to prevent internal service access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify PSK authentication configuration
    Inspect Clair's configuration files (typically clair-config.yaml or similar) for PSK-related settings. Look for 'psk', 'pre-shared-key', or 'authentication' sections in the configuration. Also check environment variables for PSK values.
    Affected if PSK is not configured, disabled, or set to an empty value - the fetcher accepts unauthenticated manifest submissions
  2. Determine installed Clair version
    Run 'clairctl version' or 'clair --version' to obtain the installed version. Compare your version against the affected version range provided in the CVE disclosure.
    Affected if Your version falls within the affected range AND PSK is not configured
  3. Confirm fetcher component is enabled
    Review your Clair configuration for the fetcher module. Check if manifest layer descriptor fetching is active. Look for 'fetcher', 'manifest', or 'layer' configuration sections.
    Affected if Fetcher is enabled and processing manifests from untrusted sources without PSK protection
  4. Inspect network egress controls
    Check if any firewall rules, network policies, or proxy configurations restrict outbound HTTP requests from the Clair service to internal services or cloud metadata endpoints (169.254.169.254).
    Affected if No network filtering blocks requests to internal services or metadata IPs

You are affected if PSK authentication is not configured and your Clair version is within the affected range - the fetcher will accept unauthenticated manifest submissions with URIs pointing to internal services.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable and configure PSK authentication for Clair to block unauthenticated manifest submissions. Consider implementing network-level filtering to restrict the fetcher's outbound HTTP capabilities to prevent internal service access.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10517 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10517 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data