CVE-2026-32590: 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…

PriorityP260high8.8CVSS 3.1

AVNACLPRLUINSUCHIHAH

EPSS

0.41%

33.5th percentile

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.

Affected

2 ranges

Vendor	Product	Version range	Fixed in
redhat	mirror_registry_for_red_hat_openshift	—	—
redhat	quay	—	—

Detection & IOCsextracted from sources · hover to see the quote

→Detect unsafe pickle deserialization of SHA hash state objects stored in the BlobUpload model database fields (sha_state, piece_sha_state). Monitor for unexpected pickle.loads() calls on data originating from these database columns. ↗
→Exploitation requires authenticated access; monitor for authenticated users initiating resumable container image layer uploads (PATCH/PUT requests to the registry blob upload endpoint) with tampered payloads, particularly against mirror-registry or Red Hat Quay 3 instances. ↗
→Focus detection on the BlobUpload model's sha_state and piece_sha_state database columns in Red Hat Quay v3.12.x for tampered/malicious pickle payloads that could trigger RCE upon deserialization. ↗
→Monitor the BlobUpload functionality / affected database column sha_state in Mirror Registry for OpenShift for anomalous or oversized serialized data that does not conform to expected hashlib state structure. ↗

·Exploitation is limited to authenticated users only; unauthenticated remote exploitation is not possible. Scope detection efforts to authenticated sessions. ↗
·The vulnerability is confirmed in Red Hat Quay v3.12.x specifically. Affected packages include quay/quay-rhel8, quay/quay-rhel9, openshift/mirror-registry-rhel8 (mirror registry for Red Hat OpenShift and OpenShift 2). ↗
·The attack vector is the resumable container image layer upload process; the malicious pickle payload must be injected into the database fields used to store intermediate upload state, not directly via a network request payload alone. ↗

CVSS provenance

nvdv3.18.8HIGHCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

vendor_redhat7.1HIGH

Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.