Skip to main content

Red Hat Quay CVE-2026-16910

| EUVDEUVD-2026-48503 MEDIUM
Server-Side Request Forgery (SSRF) (CWE-918)
2026-07-24 redhat GHSA-6j6h-vfwh-mxgx
5.5
CVSS 3.1 · Vendor: redhat
Share

Severity by source

Vendor (redhat) PRIMARY
5.5 MEDIUM
AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
vuln.today AI
5.5 MEDIUM

Repository admin access (PR:H) required to set webhook URLs; scope changes (S:C) because worker contacts internal services beyond application boundary.

3.1 AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N
Red Hat
5.5 MEDIUM
qualitative

Primary rating from Vendor (redhat).

CVSS VectorVendor: redhat

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

Lifecycle Timeline

1
Analysis Generated
Jul 24, 2026 - 07:52 vuln.today

DescriptionCVE.org

A flaw was found in Red Hat Quay's notification webhook feature. The Slack and generic webhook notification handlers accept user-supplied URLs without SSRF validation, allowing a repository administrator to make the Quay worker issue POST requests to internal network addresses or cloud infrastructure endpoints that should not be reachable from the application.

AnalysisAI

Server-Side Request Forgery (SSRF) in Red Hat Quay 3's notification webhook feature allows repository administrators to weaponize the Quay worker process as an internal network proxy. By supplying attacker-controlled URLs to the Slack or generic webhook notification handlers, a repository admin can cause the Quay backend to issue POST requests to RFC-1918 addresses, cloud metadata endpoints (e.g., AWS IMDSv1 at 169.254.169.254), or other infrastructure that should be network-isolated from the application. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.

Technical ContextAI

CWE-918 (Server-Side Request Forgery) arises when an application fetches a user-supplied URL server-side without validating the destination against an allowlist or blocking private address ranges. Red Hat Quay 3 (cpe:2.3:a:red_hat:red_hat_quay_3) and the Red Hat OpenShift Update Service (cpe:2.3:a:red_hat:red_hat_openshift_update_service) implement an event notification system that dispatches webhook POST callbacks to external URLs upon repository events. The Slack handler and the generic webhook handler both pass the administrator-supplied URL directly to the worker's HTTP client without SSRF mitigations such as DNS rebinding protection, IP allowlisting, or redirect-following controls. Because Quay workers typically execute within a Kubernetes or OpenShift cluster with broad internal network access, the blast radius of a successful SSRF extends to the entire cluster-internal network and any cloud-provider metadata services reachable from the pod.

RemediationAI

Apply the vendor-supplied patch when released; monitor https://access.redhat.com/security/cve/CVE-2026-16910 for an updated advisory with a confirmed fixed version, as no exact patch version is confirmed from the currently available data. Until a patch is applied, administrators should implement egress-level controls on Quay worker pods: configure Kubernetes NetworkPolicy to restrict outbound traffic from Quay worker pods to only known external webhook destinations, blocking access to RFC-1918 ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) and link-local addresses (169.254.0.0/16). For cloud deployments, consider IMDSv2 enforcement (AWS) or equivalent metadata endpoint hardening to reduce the value of SSRF pivots even if the network policy is incomplete. As an operational control, audit all existing Quay webhook notification configurations and remove any entries pointing to non-public IP addresses or unrecognized URLs. Restricting the repository administrator role to a minimal trusted set of users reduces the attack surface until a patch is available. Note that NetworkPolicy changes may affect legitimate webhook delivery and should be tested against expected notification destinations before enforcement.

Vendor StatusVendor

Share

CVE-2026-16910 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy