CVE-2026-10052 json
Quay/config-tool: quay/config-tool: ssrf via unfiltered ldap and smtp config validation endpoints
published 2026-05-29 5 mo ago modified 2026-11-01 8 d ago also EUVD-2026-33260
- cvss
- 4.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
A flaw was found in the Quay config-tool's LDAP and SMTP validation functions. An attacker with config editor access can exploit these functions, which make outbound connections to user-supplied endpoints without proper IP or host filtering. This allows the attacker to perform internal network reconnaissance from the Quay pod's network position, potentially mapping the internal network infrastructure.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-10052 updated cvss 4.1
quay/config-tool: quay/config-tool: SSRF via unfiltered LDAP and SMTP config validation endpoints
-
Red Hat Quay 3 quay/quay-rhel8, quay/quay-rhel9affected: no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.1 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N |
Affected products
- Red Hat Red Hat Quay 3
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
access.redhat.com
/security/cve/CVE-2026-10052
vdb-entry
-
bugzilla.redhat.com
/show_bug.cgi?id=2483157
issue-tracking
Sources
- CVE List CVE-2026-10052
- NVD CVE-2026-10052
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.