LiveActive security incident?Get immediate response
CVE Record

CVE-2026-2377: Mirror-registry: quay: quay: server-side request forgery via log export functionality

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.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

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.
Prepared
Confidence
high
Sources
11

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.

Open ATT&CK lookup
description · low confidence lookup

Cloud metadata behavior lookup

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-2377 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

2CVSS vectors
7Timeline events
2ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

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.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6redhat
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2026-2377Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Reported to Red Hat.

  3. Source timelineredhat

    Reported to Red Hat.

  4. ADP timelineredhat-SADP

    Made public.

  5. Source timelineredhat

    Made public.

  6. CVE publishedCVE Program

    The CVE record was published.

  7. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPmirror-registry: quay: quay: Server-Side Request Forgery via log export functionality
other:Red Hat severity ratingcvssV3_1
  • 2026-02-11T21:02:44.495Z: Reported to Red Hat.
  • 2026-04-08T16:18:10.324Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Red HatRed Hat Quay 3.10quay/quay-rhel8, 1779822261affected
Red HatRed Hat Quay 3.12quay/quay-rhel8, 1779811412affected
Red HatRed Hat Quay 3.14quay/quay-rhel8, 1779689392affected
Red HatRed Hat Quay 3.15quay/quay-rhel8, 1780891395affected
Red HatRed Hat Quay 3.16quay/quay-rhel9, 1779204086affected
Red HatRed Hat Quay 3.9quay/quay-rhel8, 1779811473affected
Red Hatmirror registry for Red Hat OpenShiftopenshift/mirror-registry-rhel8affected
Red Hatmirror registry for Red Hat OpenShift 2openshift/mirror-registry-rhel8affected
Weakness

CWE details

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.