dbcve.org
Mirror Registry For Red Hat OpenshiftApplication · Redhat

CVE-2026-2377

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in Red Hat Quay and mirror registry for Red Hat OpenShift. The log export feature in these products allows an authenticated user to specify an arbitrary callback URL. A backend process then makes server-side HTTP requests to this provided URL. This vulnerability, known as Server-Side Request Forgery (SSRF), could allow an attacker to send requests from the application's internal network, potentially leading to the disclosure of sensitive information.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Red Hat Quay and mirror registry for OpenShift contain an SSRF vulnerability in the log export feature. An authenticated user can supply an arbitrary callback URL, causing the backend to make server-side HTTP requests from the application's internal network to attacker-controlled destinations, potentially exposing internal services or sensitive data.

MitigationImplement strict URL validation and allowlisting for the callback URL parameter in the log export feature. Restrict outbound HTTP requests to approved domains or disable user-supplied URL functionality entirely.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mirror Registry For Red Hat OpenshiftApplication
Affected:all versions= 2.0
QuayApplication
Affected:= 3.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Red Hat Quay or Mirror Registry installation
    Check for running Quay or Mirror Registry services: 'kubectl get pods -n quay' or 'systemctl list-units | grep -i quay' or inspect container images for 'quay' or 'mirror-registry'
    Affected if Either Red Hat Quay or Mirror Registry is deployed in the environment
  2. Verify product version
    For Quay: check the image tag or deployment config 'oc get deployment -n quay -o yaml | grep image' or check '/api/v1/version' endpoint. For Mirror Registry: check '/api/v1/superuser/initialize' response or RPM package version
    Affected if Version is 3.0.0 for Quay, or any version of Mirror Registry for OpenShift
  3. Confirm log export feature is accessible
    Check if the /api/v1/export logs endpoint exists: 'curl -k https://<quay-host>/api/v1/export' (requires authentication). Inspect Quay config for 'FEATURE_EXPORT_LOGS' setting
    Affected if Log export API endpoint responds to authenticated requests (HTTP 200)
  4. Inspect audit logs for callback URL patterns
    Review Quay/Mirror Registry audit logs in database or logs directory for entries containing 'callback' or 'url' in export logs requests. Query: 'SELECT * FROM logentry WHERE context LIKE %export%'
    Affected if Audit logs show log export requests with user-supplied callback URLs pointing to external/unexpected domains
  5. Check for unusual outbound HTTP traffic
    Review network logs, proxies, or service mesh telemetry for outbound requests from Quay/Mirror Registry pods to unexpected internal or external IPs, especially on ports 80/443
    Affected if Outbound HTTP requests are observed from the application to arbitrary URLs not in an allowlist

The environment is affected if Red Hat Quay 3.0.0 or any version of Mirror Registry is deployed AND the log export feature is accessible to authenticated users, allowing them to supply arbitrary callback URLs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict URL validation and allowlisting for the callback URL parameter in the log export feature. Restrict outbound HTTP requests to approved domains or disable user-supplied URL functionality entirely.

Fix this in Mirror Registry For Red Hat Openshift Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2377 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2377 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data