CVE-2026-10052
Description
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Quay config-tool LDAP/SMTP validators allow SSRF, enabling internal network reconnaissance from the Quay pod by an attacker with config editor access.
Vulnerability
A flaw in the Quay config-tool's LDAP and SMTP validation functions, located in pkg/lib/shared/validators.go, allows server-side request forgery (SSRF). The functions ValidateEmailServer (calls net.DialTimeout to the configured mail server) and ValidateLDAPServer (calls ldap.DialURL to the configured LDAP URI) make outbound connections to user-supplied endpoints without performing IP or host filtering. This affects Quay versions up to and including 3.16, where the config editor web application is present; in Quay 3.17 and later, the config editor was removed, limiting the attack vector to CLI or container startup scenarios [1][2].
Exploitation
An attacker with config editor access (gained via HTTP Basic Authentication on the config-tool editor) can supply arbitrary LDAP or SMTP server addresses. The attacker triggers the validation functions, which attempt to connect to the supplied endpoints. No special network position is required beyond access to the Quay config-tool editor. The LDAP validator also accepts the ldapi:// scheme and reflects LDAP result codes in error messages, which could aid in reconnaissance [2].
Impact
Successful exploitation allows the attacker to perform internal network reconnaissance from the Quay pod's network position. The attacker can identify reachable internal hosts and services, potentially mapping the internal network infrastructure. This is a medium-severity information disclosure issue, as it reveals network topology and service availability [1][2].
Mitigation
Red Hat has not announced a specific fixed version. Affected users should consider removing or securing the config-tool editor (disabled by default in Quay 3.17+). As a workaround, restrict network access to the Quay pod and implement strict outbound firewall rules. The config editor web application was removed in Quay 3.17, eliminating the primary attack vector [2]. No CVE has been added to the KEV catalog at this time.
AI Insight generated on May 29, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
0No patches discovered yet.
Vulnerability mechanics
Root cause
"Missing IP/host filtering in LDAP and SMTP validation functions allows SSRF to internal network endpoints."
Attack vector
An attacker with config editor access (HTTP Basic Auth on the config-tool editor, Quay <= 3.16) supplies a malicious LDAP URI or SMTP hostname pointing to an internal network address. The validation functions make outbound connections to the attacker-controlled endpoint, allowing the attacker to probe internal services from the Quay pod's network position [ref_id=1]. The LDAP validator also accepts the `ldapi://` scheme and reflects LDAP result codes in error messages, which can leak information about reachable internal hosts [ref_id=1].
Affected code
The vulnerable functions are `ValidateEmailServer` and `ValidateLDAPServer` in `pkg/lib/shared/validators.go`. `ValidateEmailServer` calls `net.DialTimeout` to the configured mail server, and `ValidateLDAPServer` calls `ldap.DialURL` to the configured LDAP URI, both without any IP or host filtering [ref_id=1].
What the fix does
The advisory does not include a patch diff. The recommended remediation is to add IP/host filtering to the `ValidateEmailServer` and `ValidateLDAPServer` functions so they reject connections to private or loopback addresses. The config editor web application was removed in Quay 3.17, which limits the attack vector to CLI or container startup in newer versions [ref_id=1].
Preconditions
- authAttacker must have config editor access (HTTP Basic Auth on the config-tool editor)
- configQuay version <= 3.16 (config editor web app present)
Generated on May 29, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
2News mentions
0No linked articles in our index yet.