CVE-2026-15927: Server-Side Request Forgery (SSRF) in Red Hat Red Hat Quay 3.1
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.
AI Analysis
Technical Summary
CVE-2026-15927 is a Server-Side Request Forgery (SSRF) vulnerability in Red Hat Quay prior to version 3.9.25. The POST and PUT handlers in endpoints/api/mirror.py accept an external_reference parameter without proper SSRF validation, unlike organization-level mirror handlers which apply validation. This allows a repository administrator to craft hostnames that cause the Quay mirror worker to make requests via Skopeo to internal network services, cloud metadata endpoints, or other unintended resources. The vulnerability requires authenticated repository administrator privileges and can expose sensitive internal resources. The CVSS v3.1 base score is 6.8 (medium severity) with network attack vector, low attack complexity, high privileges required, no user interaction, changed scope, and high confidentiality impact. Red Hat has released Quay version 3.9.25 with fixes for this vulnerability.
Potential Impact
An authenticated repository administrator can exploit this SSRF vulnerability to cause the Quay mirror worker to connect to internal network services or cloud metadata endpoints that are not intended to be accessible. This can lead to exposure of sensitive internal resources. The vulnerability does not impact integrity or availability but has a high confidentiality impact. The risk is limited to users with repository administrator privileges.
Mitigation Recommendations
Red Hat has released Quay version 3.9.25 which fixes this vulnerability. Users should upgrade to version 3.9.25 or later. Additional mitigations include restricting network egress from Quay mirror worker pods or containers using network policies or firewall rules to block access to internal network ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) and cloud metadata endpoints (169.254.169.254, metadata.google.internal). Limit repository creation and administrator privileges to trusted users via Quay's RBAC configuration. If repository-level mirroring is not required, disable the feature or restrict access to mirror API endpoints through a reverse proxy.
CVE-2026-15927: Server-Side Request Forgery (SSRF) in Red Hat Red Hat Quay 3.1
Description
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.
CVSS v3.1
Score 6.8medium
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-15927 is a Server-Side Request Forgery (SSRF) vulnerability in Red Hat Quay prior to version 3.9.25. The POST and PUT handlers in endpoints/api/mirror.py accept an external_reference parameter without proper SSRF validation, unlike organization-level mirror handlers which apply validation. This allows a repository administrator to craft hostnames that cause the Quay mirror worker to make requests via Skopeo to internal network services, cloud metadata endpoints, or other unintended resources. The vulnerability requires authenticated repository administrator privileges and can expose sensitive internal resources. The CVSS v3.1 base score is 6.8 (medium severity) with network attack vector, low attack complexity, high privileges required, no user interaction, changed scope, and high confidentiality impact. Red Hat has released Quay version 3.9.25 with fixes for this vulnerability.
Potential Impact
An authenticated repository administrator can exploit this SSRF vulnerability to cause the Quay mirror worker to connect to internal network services or cloud metadata endpoints that are not intended to be accessible. This can lead to exposure of sensitive internal resources. The vulnerability does not impact integrity or availability but has a high confidentiality impact. The risk is limited to users with repository administrator privileges.
Mitigation Recommendations
Red Hat has released Quay version 3.9.25 which fixes this vulnerability. Users should upgrade to version 3.9.25 or later. Additional mitigations include restricting network egress from Quay mirror worker pods or containers using network policies or firewall rules to block access to internal network ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) and cloud metadata endpoints (169.254.169.254, metadata.google.internal). Limit repository creation and administrator privileges to trusted users via Quay's RBAC configuration. If repository-level mirroring is not required, disable the feature or restrict access to mirror API endpoints through a reverse proxy.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- redhat
- Date Reserved
- 2026-07-16T06:31:41.405Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-15927","vendor":"Red Hat"}]
Threat ID: 6a5f06c72a4a8d59899adb6c
Added to database: 07/21/2026, 05:42:31 UTC
Last enriched: 08/13/2026, 13:39:10 UTC
Last updated: 09/01/2026, 22:52:09 UTC
Views: 78
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.