Bug 2579590 (CVE-2026-133958)

Summary: CVE-2026-133958 quay: quay: webhook notifications allow SSRF via incomplete hostname validation
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: aruklets, bcaton, doconnor, shudeshp
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in Quay. Insufficient validation of repository notification webhook URLs allows an authenticated administrator to trigger Server-Side Request Forgery (SSRF). By specifying an internal URL or a redirect to an internal destination, an attacker can force the Quay worker to issue unauthorized HTTP requests to internal network locations and cloud metadata services.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-11-20 18:11:33 UTC
A flaw was found in Quay's repository notification webhook delivery path. WebhookMethod in notifications/notificationmethod.py validates user-supplied callback URLs using only a hostname string blocklist (HOSTNAME_BLACKLIST: localhost, 127.0.0.1, plus WEBHOOK_HOSTNAME_BLACKLIST). It does not resolve DNS or reject RFC 1918, loopback, link-local, or cloud-metadata destinations. Unlike mirror, proxy-cache, and export-log callback flows, this path does not call validate_external_registry_url() in util/security/ssrf.py. Delivery then uses requests.post() with the default allow_redirects=True, so a public URL that passes the name check can respond with a 302/307 to an internal address and the notification worker will follow it without re-validation. An authenticated repository administrator who can create webhook notifications can cause the Quay worker to issue HTTP requests to internal network locations, including cloud instance metadata endpoints where reachable, resulting in server-side request forgery.