CVE-2026-10052: Quay/config-tool: quay/config-tool: ssrf via unfiltered ldap and smtp config validation endpoints

Published May 29, 2026
·
Updated

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.

Other sources

The Quay config-tool's LDAP and SMTP validation functions in pkg/lib/shared/validators.go make outbound connections to user-supplied endpoints with no IP/host filtering. ValidateEmailServer calls net.DialTimeout to the configured mail server, and ValidateLDAPServer calls ldap.DialURL to the configured LDAP URI. An attacker with config editor access (HTTP Basic Auth on the config-tool editor, Quay <= 3.16) can exploit these to perform internal network reconnaissance from the Quay pod's network position. The config editor web application was removed in Quay 3.17, limiting the attack vector to CLI or container startup in newer versions. The LDAP validator also accepts the ldapi:// scheme and reflects LDAP result codes in error messages. The GitLab OAuth validator separately exposes clientsecret in URL querystrings (CWE-598).

Red Hat

Affected Software

1 affected component
Quay Quay config-tool<=3.16

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Quay/config-tool to a version that resolves this vulnerability.

    Fixed in 3.17
  2. Compensating control

    Restrict access to the Quay config-tool config editor (HTTP Basic Auth on the config-tool editor) to prevent attackers from reaching the LDAP/SMTP validation endpoints that make outbound connections to user-supplied endpoints without IP/host filtering.

Event History

May 29, 2026
Data Sourced
via Red Hat·07:35 AM
DescriptionSeverityAffected Software
CVE Published
via MITRE·07:59 AM
Data Sourced
via MITRE·07:59 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:16 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2026-10052?

The severity of CVE-2026-10052 is rated as medium with a score of 4.1.

2

How do I fix CVE-2026-10052?

To fix CVE-2026-10052, ensure that proper IP or host filtering is implemented in the Quay config-tool's LDAP and SMTP validation functions.

3

What are the potential impacts of CVE-2026-10052?

The potential impacts of CVE-2026-10052 include unauthorized internal network reconnaissance due to improper handling of outbound connections.

4

Who can exploit CVE-2026-10052?

An attacker with config editor access can exploit CVE-2026-10052 due to the lack of adequate filtering.

5

What type of vulnerability is CVE-2026-10052 classified as?

CVE-2026-10052 is classified as a Server Side Request Forgery (SSRF) vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203