CVE-2026-85471 — Quay: quay: webhook notification ssrf -- hostname-string blocklist trivially bypassable
A flaw was found in Quay. An authenticated repository administrator could bypass the hostname blacklist in webhook notifications, leading to a Server-Side Request Forgery (SSRF) vulnerability. This allows the Quay application to be tricked into sending requests to internal network resources, such as cloud metadata services or other services within the cluster. Consequently, this could lead to the disclosure of sensitive information from these internal services.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Red Hat Mirror Registry For Red Hat Openshift, Red Hat mirror registry for Red Hat OpenShift 2, Red Hat Red Hat Quay 3).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (ssrf), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Red Hat | Mirror Registry For Red Hat Openshift | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | mirror registry for Red Hat OpenShift 2 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat Quay 3 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.4 | CVSS 3.1 | Medium | 3.1 | 2.7 | secalert@redhat.com via NIST National Vulnerability Database |
| 6.4 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
| 6.4 | CVSS 3.1 | Medium | — | — | redhat via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N (score shown at the top: secalert@redhat.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor outbound requests from the server to internal IPs and cloud metadata endpoints.
Timeline
What happened to this CVE, newest first.
- 2026
- Source status changed · Received → Awaiting Analysis
- SSVC assessment updated
- Affected products added · red hat/mirror registry for red hat openshift, red hat/mirror registry for red hat openshift 2, red hat/red hat quay 3
- Record published
- CVSS changed · 6.4
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
4 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-109194 Quay: build trigger uuid idor in quay api 3d
- Low CVE-2026-109195 Quay: repository auto-prune policy uuid idor in quay api 3d
- Medium CVE-2026-105447 Quay: quay: global read-only superuser can access build trigger write credentials 10d
- Medium CVE-2026-102576 Quay: quay: dom-based cross-site scripting via unvalidated redirect_url on signin page 10d
- Medium CVE-2026-102295 Quay: quay: dom-based cross-site scripting via oauth local callback format=json parameter 10d
- Medium CVE-2026-16910 Quay: ssrf in red hat quay notification webhooks (slack/generic) Jul 24, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-85471 is "Quay: quay: webhook notification ssrf -- hostname-string blocklist trivially bypassable", rated Medium. It affects Mirror Registry For Red Hat Openshift (Red Hat); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.4 describes technical severity. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.