Skip to content
Fencer Vulns
medium 5.5

CVE-2026-16910 json

Quay: ssrf in red hat quay notification webhooks (slack/generic)

published 2026-07-24 3 mo ago modified 2026-11-01 8 d ago also EUVD-2026-48503

cvss
5.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 21%
public exploits
0
none known

Summary

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.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-16910 updated cvss 5.5

quay: SSRF in Red Hat Quay notification webhooks (Slack/generic)

  • Red Hat OpenShift Update Service openshift-update-service/openshift-update-service-rhel8 Red Hat Quay 3 quay/quay-rhel9
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Quay 3 quay/quay-rhel8
    under investigation

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
3 mo ago

Exploit prediction

0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.5 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N

Affected products

  • Red Hat Red Hat OpenShift Update Service
  • Red Hat Red Hat Quay 3

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.