SSRF (Server-Side Request Forgery) in Quay config-tool's LDAP and SMTP validation functions (CVE-2026-10052)
Summary
SSRF in Quay config-tool's LDAP and SMTP validation functions (CVE-2026-10052). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-10052 has been found in Quay config-tool's LDAP and SMTP validation functions.
Risk of unauthorized operations or information disclosure. CVSS score: 4.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Quay config-tool's LDAP and SMTP validation functions CVE-2026-10052" on the vendor's site.
CVE-2026-10052 (Quay config-tool's LDAP and SMTP validation functions) — CWE-918 / CVSS v3 4.1
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in Quay config-tool's LDAP and SMTP validation functions.
Check the vendor advisory for the affected versions of Quay config-tool's LDAP and SMTP validation functions.
Severity: Medium (CVSS 4.1/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Quay config-tool's LDAP and SMTP validation functions を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web secalert@redhat.com
- web secalert@redhat.com
- web github.com