CVE-2026-85471
6.4MediumPublished 12 Oct 2026 · NVD status: Awaiting Analysis · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Impact
- Limited impact
- Weakness
- CWE-918
Impact
Authenticated repository administrators can trigger Server-Side Request Forgery (SSRF) requests from Quay to internal services, potentially exposing sensitive data like cloud metadata. An attacker needs valid repository admin credentials on the target Quay instance.
Root cause
The webhook notification mechanism fails to properly enforce hostname blacklist restrictions, allowing malicious hosts to bypass validation.
Affected systems
Versions not listed — check the vendor advisory.
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Fix & remediation
Upgrade Quay to the patched version as specified in Red Hat advisory CVE-2026-85471 once published. As an interim workaround, restrict egress network traffic from the Quay application pods to cloud metadata IPs (e.g., 169.254.169.254) and internal service ranges using network policies or firewall rules.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
A flaw was found in Quay. An authenticated repository administrator could bypass the hostname blacklist in webhook notifications, leading to a Server-Side Request Forgery (SSRF) vulnerability. This allows the Quay application to be tricked into sending requests to internal network resources, such as cloud metadata services or other services within the cluster. Consequently, this could lead to the disclosure of sensitive information from these internal services.