Skip to main content
Vulnerability Database/CVE-2026-85471

CVE-2026-85471: Quay Webhook SSRF Vulnerability

CVE-2026-85471 is an SSRF flaw in Quay that lets authenticated admins bypass webhook hostname blacklists to access internal resources. This article covers the technical details, affected versions, security impact, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-85471 Overview

A Server-Side Request Forgery (SSRF) vulnerability affects Red Hat Quay container image registry. An authenticated repository administrator can bypass the hostname blacklist enforced on webhook notifications. The bypass allows the Quay application to issue requests to internal network resources, including cloud metadata services and in-cluster workloads. Successful exploitation can expose sensitive internal data to the attacker.

The weakness is classified as CWE-918: Server-Side Request Forgery. It requires authentication and administrative access to a repository, which limits the attack population but not the blast radius inside a cluster.

Critical Impact

An authenticated repository administrator can coerce Quay into contacting internal services, enabling retrieval of cloud metadata credentials and other in-cluster secrets.

Affected Products

  • Red Hat Quay (container image registry)
  • Quay deployments configured with webhook notifications
  • Quay instances running in cloud environments exposing instance metadata services

Discovery Timeline

  • 2026-10-12 - CVE-2026-85471 published to the National Vulnerability Database
  • 2026-10-15 - Last updated in NVD database

Technical Details for CVE-2026-85471

Vulnerability Analysis

Quay supports webhook notifications that fire on repository events such as image pushes or vulnerability findings. The webhook subsystem applies a hostname blacklist intended to prevent notifications from targeting internal or loopback addresses. The blacklist filter is incomplete, allowing a repository administrator to craft a webhook target that resolves to a restricted internal destination despite the filter.

Once the request is dispatched, the Quay backend acts as an unintended proxy. The response, redirect chain, or error metadata can leak information from systems that trust requests originating from inside the trust boundary. In cloud deployments, this includes the Instance Metadata Service (IMDS) endpoint, which may return temporary credentials bound to the Quay workload identity.

The scope-changed CVSS vector reflects that the impacted component (an internal service) differs from the vulnerable component (Quay). Confidentiality and integrity are rated low because leaked data varies by environment and the attacker cannot directly execute code.

Root Cause

The root cause is incomplete input validation in the webhook target handler. The blacklist operates on textual hostname patterns rather than resolved IP addresses. Alternate encodings, DNS entries that resolve to RFC 1918 ranges, or redirect chains that terminate at internal addresses defeat the filter.

Attack Vector

An authenticated user holding the administrator role on a Quay repository configures a notification webhook. The attacker supplies a URL that passes the hostname blacklist check but, after DNS resolution or HTTP redirection, points at 169.254.169.254, a 127.0.0.0/8 address, or a cluster-internal service. Triggering a repository event causes Quay to issue the outbound request. Returned data, timing, or error content discloses details about the internal target.

No verified public exploit code is available for this issue. See the Red Hat CVE-2026-85471 Advisory and Red Hat Bug Report #2528221 for authoritative technical details.

Detection Methods for CVE-2026-85471

Indicators of Compromise

  • Webhook configurations whose target hostname resolves to RFC 1918, link-local, or loopback addresses.
  • Outbound HTTP connections from the Quay application pod to 169.254.169.254 or other metadata endpoints.
  • Webhook delivery logs showing redirects terminating at internal IP ranges.
  • New or modified repository notifications created by administrator accounts shortly before anomalous egress.

Detection Strategies

  • Audit the Quay notification configuration table for webhook URLs that fail a strict post-resolution IP allowlist.
  • Instrument the Quay application network namespace to log all egress destinations and alert on private or metadata ranges.
  • Correlate repository administrator activity with webhook creation events and subsequent outbound traffic patterns.

Monitoring Recommendations

  • Forward Quay application and audit logs into a centralized analytics tier for correlation with network telemetry.
  • Monitor cloud provider audit logs for use of IMDS-issued credentials from unexpected source identities.
  • Alert on webhook notification failures that reference internal hostnames, loopback addresses, or metadata service responses.

How to Mitigate CVE-2026-85471

Immediate Actions Required

  • Apply the Red Hat Quay update referenced in the Red Hat CVE-2026-85471 Advisory as soon as it is available for your channel.
  • Review every existing webhook configuration and remove entries pointing at non-public destinations.
  • Rotate any cloud credentials associated with the Quay workload identity if metadata service exposure is suspected.
  • Restrict the repository administrator role to a minimum set of trusted operators.

Patch Information

Refer to the Red Hat CVE-2026-85471 Advisory for the authoritative list of fixed versions and errata. The Red Hat Bug Report #2528221 tracks the upstream remediation. Prioritize patching Quay instances deployed in cloud environments where IMDS endpoints are reachable from the application pod.

Workarounds

  • Enforce IMDSv2 with hop-limit of 1 on AWS, or the equivalent metadata hardening on Azure and Google Cloud, to blunt credential theft.
  • Apply a network policy that blocks egress from the Quay pod to RFC 1918, link-local, and loopback ranges except for explicit allowlisted services.
  • Route outbound webhook traffic through an egress proxy that re-validates the resolved destination IP against an allowlist.
  • Temporarily disable the webhook notification feature if administrator trust cannot be guaranteed.
bash
# Example Kubernetes NetworkPolicy fragment denying egress to IMDS
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: quay-block-metadata-egress
  namespace: quay-enterprise
spec:
  podSelector:
    matchLabels:
      app: quay-app
  policyTypes:
    - Egress
  egress:
    - to:
        - ipBlock:
            cidr: 0.0.0.0/0
            except:
              - 169.254.0.0/16
              - 127.0.0.0/8
              - 10.0.0.0/8
              - 172.16.0.0/12
              - 192.168.0.0/16

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.