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.
Security readout for executives and security teams
Plain-English summary
An authenticated user could make affected Red Hat Quay or mirror registry servers call a URL of the user’s choice through log export. That can expose information reachable from the registry’s internal network. The issue is medium severity, but it matters where the registry can reach sensitive internal services.
Executive priority
Treat as a timely patching and exposure-reduction item, especially for registries in sensitive internal networks. It is not marked as actively exploited in the provided sources, but confidentiality impact can be meaningful in poorly segmented environments.
Technical view
CVE-2026-2377 is an SSRF in log export callback handling. A low-privileged authenticated user can provide an arbitrary callback URL, and a backend process sends HTTP requests to it. Red Hat rates it CVSS 6.5 with high confidentiality impact and no integrity or availability impact stated.
Likely exposure
Exposure is limited to Red Hat Quay 3.9 through 3.16 and mirror registry for Red Hat OpenShift deployments listed by Red Hat. Risk increases when authenticated registry users are broad and the registry backend can reach metadata endpoints, internal APIs, or sensitive services.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires authentication and access to the log export feature. The practical impact depends on internal network reachability from the backend process.
Researcher notes
Key unknowns are the exact fixed versions and any product-specific configuration mitigations, which should be taken from Red Hat errata. Avoid assuming impact beyond SSRF-enabled information disclosure from the backend network context.
Mitigation direction
Apply the relevant Red Hat security advisory updates for affected Quay or mirror registry deployments.
Review Red Hat CVE and errata pages for product-specific fixed images or packages.
Restrict log export access to trusted authenticated users until patched.
Limit registry backend egress to required destinations only.
Monitor backend outbound requests for unusual internal or metadata-service destinations.
Validation and detection
Inventory Quay and mirror registry deployments against the affected Red Hat product list.
Confirm deployed image or package versions against the relevant Red Hat errata.
Review role assignments for users who can access log export functionality.
Check outbound proxy, firewall, or network logs for unexpected backend HTTP requests.
Verify compensating egress controls block access to sensitive internal endpoints.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-918 · source CWE mapping
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.