Bug 2579590 (CVE-2026-133958) - CVE-2026-133958 quay: quay: webhook notifications allow SSRF via incomplete hostname validation
Summary: CVE-2026-133958 quay: quay: webhook notifications allow SSRF via incomplete h...
Keywords:
Status: NEW
Alias: CVE-2026-133958
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-20 18:11 UTC by OSIDB Bzimport
Modified: 2026-11-21 04:18 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.