A flaw was found in Red Hat Quay's repository-level mirror configuration feature. The POST and PUT handlers in endpoints/api/mirror.py accept an external_reference parameter without SSRF validation, unlike the organization-level mirror handlers which apply validate_external_registry_url(). A repository administrator can supply a crafted hostname that causes the Quay mirror worker to make requests via Skopeo to internal network services, cloud metadata endpoints, or other resources not intended to be reachable from the Quay application.
CVE-2026-15927
Score 6.8 from GitHub Security Advisory published 2026-07-21. a secondary CVSS source baseline 6.8; 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
- 6.8
- EG Score
- 6.8(high)
- EG Risk
- 31(Track)EG Risk 31/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 computedSeverity68% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 14.1%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 21, 2026
Advisory Details (2)
Auto-updated Jul 21, 20262501256 – (CVE-2026-15927) CVE-2026-15927 quay: mirror-registry: SSRF: repo-level mirror accepts external_reference without URL validation
https://bugzilla.redhat.com/show_bug.cgi?id=2501256Vendor Advisories for CVE-2026-15927(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 12× in last 7d / 12× 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-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:05 UTCEG score recompute
- 2026-07-22 23:23 UTCEG score recompute
- 2026-07-22 23:23 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-21 06:49 UTCEG score recompute
- 2026-07-21 06:49 UTCGHSA enrichment
- 2026-07-21 05:45 UTCEG score recompute
- 2026-07-21 05:43 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
Frequently asked(5)
What is CVE-2026-15927?
When was CVE-2026-15927 disclosed?
Is CVE-2026-15927 actively exploited?
What is the CVSS score of CVE-2026-15927?
How do I remediate CVE-2026-15927?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15927
Is Your Infrastructure Affected by CVE-2026-15927?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.