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.
CVE-2026-16910
Score 5.5 from GitHub Security Advisory published 2026-07-24. a secondary CVSS source baseline 5.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.5
- EG Score
- 5.5(high)
- EG Risk
- 25(Track)EG Risk 25/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity55% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 12%
- KEV
- Not listed
Published
July 24, 2026
Last Modified
July 24, 2026
Advisory Details (2)
Auto-updated Jul 24, 20262506685 – (CVE-2026-16910) CVE-2026-16910 quay: SSRF in Red Hat Quay notification webhooks (Slack/generic)
https://bugzilla.redhat.com/show_bug.cgi?id=2506685Vendor Advisories for CVE-2026-16910(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 16× in last 7d / 16× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-29 06:15 UTCEG score recompute
- 2026-07-29 06:15 UTCGHSA enrichment
- 2026-07-28 05:12 UTCEG score recompute
- 2026-07-28 05:12 UTCGHSA enrichment
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 04:08 UTCEG score recompute
- 2026-07-27 04:08 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 03:04 UTCEG score recompute
- 2026-07-26 03:04 UTCGHSA enrichment
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-24 07:27 UTCEG score recompute
- 2026-07-24 07:26 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p92CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(5)
What is CVE-2026-16910?
When was CVE-2026-16910 disclosed?
Is CVE-2026-16910 actively exploited?
What is the CVSS score of CVE-2026-16910?
How do I remediate CVE-2026-16910?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16910
Is Your Infrastructure Affected by CVE-2026-16910?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.