CVE-2026-10517

Rejected after intentional API behavior confirmation

Published Jun 1, 2026 · Updated Jun 1, 2026

Red Hat Quay is not affected because Red Hat rejected the CVE after confirming that the reported Clair API behavior is intentional. The optional PSK and unauthenticated indexer endpoint belong to Clair rather than claircore, so the original report attributed documented deployment behavior to the wrong codebase. No security defect or affected version remains in the authoritative record, and the earlier Red Hat Quay applicability, CWE, and CVSS assertions were removed.

CVSS severityUnavailable
Unscored
EPSS probabilityUnavailable
No score available in this record
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Red Hat Quay is not affected because Red Hat rejected the CVE after confirming that the reported Clair API behavior is intentional. The optional PSK and unauthenticated indexer endpoint belong to Clair rather than claircore, so the original report attributed documented deployment behavior to the wrong codebase. No security defect or affected version remains in the authoritative record, and the earlier Red Hat Quay applicability, CWE, and CVSS assertions were removed.

The record

CVE
CVE-2026-10517
Published
Jun 1, 2026
Updated
Jun 1, 2026
Vendor
389 Directory Server
Product
Red Hat Quay
Classifications
Unavailable
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Jun 1, 2026CVE publishedPublication date reported by the CVE source.
  2. Jun 1, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

389 Directory Server · Red Hat QuayAffected versions are unavailable in this record.

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo