CVE-2026-15927 mirror registry for Red Hat OpenShift 2 vulnerability
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.
Browse API Security security risksQuick answer
mirror registry for Red Hat OpenShift 2 should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Review vendor advisory for affected versions.
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-15927 affects mirror registry for Red Hat OpenShift 2 and involves server-side request forgery. Successful exploitation may make the server contact internal services or expose data that should not be reachable externally. Prioritize deployments that process untrusted input, expose the affected feature, or hold sensitive data. Apply the Red Hat Quay or mirror-registry update referenced by the advisory when available; until then, restrict repository-mirror administration and block mirror-worker access to private, loopback, and cloud-metadata addresses.
- Inventory every deployment, device, package, plugin, container, build, and environment that uses mirror registry for Red Hat OpenShift 2.
- Compare the installed package, build, firmware, or commit with the affected range in the linked vendor and NVD advisories.
- Apply the Red Hat Quay or mirror-registry update referenced by the advisory when available; until then, restrict repository-mirror administration and block mirror-worker access to private, loopback, and cloud-metadata addresses.
- Until patched, restrict URL inputs and block outbound access to private, loopback, link-local, and cloud-metadata addresses.
- Review configuration, roles, tokens, network paths, and exposed endpoints connected to mirror registry for Red Hat OpenShift 2; remove access that is not required.
- Review proxy, DNS, firewall, cloud-metadata, and application logs for requests to internal, loopback, link-local, or unusual external addresses.
- If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-15927 in place.
- Use a safe regression test to confirm the affected server-side request forgery path no longer produces the vulnerable behavior.
- Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
- Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
- Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.
Related categories
Related security risks
More published guidance from the same primary category.
Trusted references
FAQ
What is affected by CVE-2026-15927?
mirror registry for Red Hat OpenShift 2 should be checked against the vendor advisory and trusted references linked on this page.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.