CVE-2026-10517 (GCVE-0-2026-10517)
Vulnerability from cvelistv5 – Published: 2026-06-01 07:56 – Updated: 2026-07-27 08:35Retracted 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.
Show details on NVD website{
"containers": {
"cna": {
"providerMetadata": {
"dateUpdated": "2026-07-27T08:35:41.456Z",
"orgId": "53f830b8-0a3f-465b-8143-3b8a9948e749",
"shortName": "redhat"
},
"rejectedReasons": [
{
"lang": "en",
"value": "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\u0027s codebase or git history. The unauthenticated indexer API is Clair\u0027s 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."
}
]
}
},
"cveMetadata": {
"assignerOrgId": "53f830b8-0a3f-465b-8143-3b8a9948e749",
"assignerShortName": "redhat",
"cveId": "CVE-2026-10517",
"datePublished": "2026-06-01T07:56:09.156Z",
"dateRejected": "2026-07-27T08:35:41.456Z",
"dateReserved": "2026-06-01T07:25:15.700Z",
"dateUpdated": "2026-07-27T08:35:41.456Z",
"state": "REJECTED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-10517",
"date": "2026-07-27",
"epss": "0.00292",
"percentile": "0.21421"
},
"nvd": "{\"cve\":{\"id\":\"CVE-2026-10517\",\"sourceIdentifier\":\"secalert@redhat.com\",\"published\":\"2026-06-01T09:16:16.447\",\"lastModified\":\"2026-07-27T09:16:37.143\",\"vulnStatus\":\"Rejected\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"Rejected reason: 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\u0027s codebase or git history. The unauthenticated indexer API is Clair\u0027s 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.\"}],\"metrics\":{},\"references\":[]}}",
"redhat_vex": {
"current_release_date": "2026-07-27T09:34:51+00:00",
"cve": "CVE-2026-10517",
"id": "CVE-2026-10517",
"initial_release_date": "2026-04-24T00:00:00+00:00",
"product_status:known_not_affected": "1",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "clair: clair: unauthenticated SSRF via manifest layer URI enables internal network reconnaissance",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-10517.json",
"version": "3"
},
"suse_vex": {
"aggregate_severity": "moderate",
"current_release_date": "2026-06-27T02:05:39Z",
"cve": "CVE-2026-10517",
"id": "CVE-2026-10517",
"initial_release_date": "2026-06-27T02:05:39Z",
"source": "SUSE CSAF VEX",
"status": "interim",
"title": "SUSE CVE CVE-2026-10517",
"url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2026-10517.json",
"version": "2"
},
"vulnrichment": {
"containers": "{\"cna\": {\"rejectedReasons\": [{\"lang\": \"en\", \"value\": \"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\u0027s codebase or git history. The unauthenticated indexer API is Clair\u0027s 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.\"}], \"providerMetadata\": {\"orgId\": \"53f830b8-0a3f-465b-8143-3b8a9948e749\", \"shortName\": \"redhat\", \"dateUpdated\": \"2026-07-27T08:35:41.456Z\"}}}",
"cveMetadata": "{\"cveId\": \"CVE-2026-10517\", \"assignerOrgId\": \"53f830b8-0a3f-465b-8143-3b8a9948e749\", \"state\": \"REJECTED\", \"assignerShortName\": \"redhat\", \"dateReserved\": \"2026-06-01T07:25:15.700Z\", \"datePublished\": \"2026-06-01T07:56:09.156Z\", \"dateUpdated\": \"2026-07-27T08:35:41.456Z\", \"dateRejected\": \"2026-07-27T08:35:41.456Z\"}",
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.