CVE-2026-10517 Claircore: Unauthenticated attackers can submit manifests with URIs pointing to internal services or cloud metadata endpoints
Not scored
Published
Updated
Check this codebase for CVE-2026-10517 and fix it if it is affected.
What it is: CVE-2026-10517 is a vulnerability in github.com/quay/claircore, published on 1 Jun 2026.
Exploitation: There is no known exploitation of CVE-2026-10517 in the wild and no public exploit code.
Affected packages and fixed versions:
- github.com/quay/claircore (Go): affected all versions; no fix listed
- github.com/quay/claircore (Go): affected all versions up to 1.5.52; no fix listed
- github.com/quay/claircore (Go): affected all versions up to 1.5.52; no fix listed
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-10517/ (Markdown: https://insights.sbomify.com/CVE-2026-10517/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2026-10517?
CVE-2026-10517 is a vulnerability in github.com/quay/claircore, published on 1 Jun 2026.
Official 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.
Which versions are affected by CVE-2026-10517?
3 open source packages ship an affected version, including github.com/quay/claircore.
| Package | Affected | Fixed in |
|---|---|---|
github.com/quay/claircore Go | All versions | None |
github.com/quay/claircore Go | All versions to 1.5.52 | None |
github.com/quay/claircore Go | All versions to 1.5.52 | None |
How do I fix CVE-2026-10517?
Upgrade to a fixed version.
Is CVE-2026-10517 being exploited?
There is no known exploitation of CVE-2026-10517 in the wild and no public exploit code.
Sources
Also known as GHSA-698x-9w2p-7vvp, GO-2026-5939, MINI-2v3h-4m54-2x9h, MINI-65g4-c64g-4gp3, MINI-78qx-xhc2-3cwc, MINI-f7xv-3wm8-4vqr and 4 more.