CVE-2026-32590

Mirror-registry: remote code execution using pickle deserialization

Published Apr 8, 2026 CVSS 3.1 · 7.1 High EPSS < 1% KEV · Not listed
Description
A flaw was found in Red Hat Quay's handling of resumable container image layer uploads. The upload process stores intermediate data in the database using a format that, if tampered with, could allow an attacker to execute arbitrary code on the Quay server.

Analysis

AI-generated

Technical impact

The vulnerability lies in how Red Hat Quay handles resumable container image layer uploads. During the upload process the server stores intermediate data in its database in a serialized format that is not properly safeguarded. If an attacker can modify that serialized payload, the deserialization step can trigger arbitrary code execution on the Quay host, exposing the system to full compromise. The weakness is a classic unsafe deserialization flaw, classified as CWE‑502.

Affected Systems

The flaw affects Red Hat Quay version 3 and the Red Hat mirror registry used in OpenShift, with affected releases identified as mirror registry 1 and 2. Users deploying these components without a recent fix are vulnerable.

Risk and Exploitability

The CVSS base score is 7.1, indicating a high severity. EPSS data is not yet available, and the vulnerability is not in the KEV catalog, suggesting no mass exploitation yet. Nevertheless, the attack vector requires that an attacker be able to inject a crafted payload into the upload workflow, which is feasible for internal threat actors or compromised clients. Once exploited, the attacker can run arbitrary code with the permissions of the Quay service, potentially leading to full system takeover.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest Red Hat Quay 3 update that addresses the deserialization issue. 
  • Upgrade the mirror registry for OpenShift to a version that has patched the upload handling flaw. 
  • If a patch is not available, restrict network access to the upload endpoint so only trusted hosts can submit image layers. 
  • Monitor the upload logs for abnormal activity and audit the database for suspicious serialized objects. 
  • Contact Red Hat support for guidance if remediation steps are unclear.

Generated by OpenCVE AI on April 8, 2026 at 18:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:/a:redhat:mirror_registry:2 cpe:/a:redhat:mirror_registry:2.0::el8
References
Type Values Removed Values Added
CPEs cpe:/a:redhat:quay:3 cpe:/a:redhat:quay:3.14::el8
References
Type Values Removed Values Added
First Time appeared Redhat mirror Registry For Red Hat Openshift
CPEs cpe:2.3:a:redhat:mirror_registry_for_red_hat_openshift:-:*:*:*:*:*:*:*
cpe:2.3:a:redhat:mirror_registry_for_red_hat_openshift:2.0:*:*:*:*:*:*:*
cpe:2.3:a:redhat:quay:3.0.0:*:*:*:*:*:*:*
Vendors & Products Redhat mirror Registry For Red Hat Openshift
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description A flaw was found in Red Hat Quay's handling of resumable container image layer uploads. The upload process stores intermediate data in the database using a format that, if tampered with, could allow an attacker to execute arbitrary code on the Quay server.
Title Mirror-registry: remote code execution using pickle deserialization
First Time appeared Redhat
Redhat mirror Registry
Redhat quay
Weaknesses CWE-502
CPEs cpe:/a:redhat:mirror_registry:1
cpe:/a:redhat:mirror_registry:2
cpe:/a:redhat:quay:3
Vendors & Products Redhat
Redhat mirror Registry
Redhat quay
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-502

    Deserialization of Untrusted Data

Sources

Status
PUBLISHED
Assigner
redhat
Published
Updated
Sep 9, 2026, 10:38 PM
Reserved
Mar 12, 2026, 2:39 PM
Status
Modified
Published
Apr 8, 2026, 6:25 PM
Modified
Sep 9, 2026, 11:16 PM
Severity
Moderate
Public date
Apr 8, 2026, 12:00 AM