Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Evidence used
No CISA KEV confirmation is currently recorded.
EPSS is 0.79% for the current model date.
Compensating controls
Validate the affected product branch and deploy the verified fixed release.
Restrict the affected network interface to trusted sources where business-safe.
Monitor vendor guidance and exploitation sources for a material change.
Verification
Confirm that the asset runs Red Hat mirror registry for Red Hat OpenShift 2.0 and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Direct vendor intelligence
Authoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
1 current
CVE-2026-32590 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitymirror-registry: remote code execution using pickle deserialization
1 known affected
The vendor explicitly identifies these products as affected by this CVE.
openshift/mirror-registry-rhel8 as a component of mirror registry for Red Hat OpenShift
Summary
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.
Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Optional official sources
National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.
Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.
Official European source
ENISA European Vulnerability Database
Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.
1 current
ENISA EUVD identifier
EUVD-2026-20515
No EUVD known-exploited evidence
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.
EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
7.1 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch available
01
What, why and how
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.
What
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.
Why
Attacker-influenced serialised data is reconstructed as trusted objects, which can invoke dangerous application behaviour.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.
What
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.
Why
Attacker-influenced serialised data is reconstructed as trusted objects, which can invoke dangerous application behaviour.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No confirmed evidence
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.None recorded
No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
Likely attack path
a network path → Deserialization of Untrusted Data → execute code or commands in the affected security context
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
User interaction
Required interaction required
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness ?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-502: Deserialization of Untrusted Data. The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
CVSS vector ?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
NetworkRemote code executionCWE-502
A
Official authority intelligence
Only matched European and national findings are included. Language selectors and unavailable sources are omitted.
ENISA EUVD · EUVD-2026-20515Official EUVD mapping
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.
Official EUVD record ↗BSI · German · WID-SEC-2026-1856Red Hat Quay: Mehrere Schwachstellen
Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Red Hat Quay ausnutzen, um beliebigen Programmcode auszuführen und serverseitige Request-Forgery-Angriffe durchzuführen.
Official advisory ↗Cyber Security Agency of Singapore · English · CSA-SB-20260415Security Bulletin 15 April 2026
The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 15 April 2026, published on 15 April 2026. Open the linked bulletin for the product, severity and reference information published in that issue.
Official advisory ↗JVN iPedia · Japanese · JVNDB-2026-012196レッドハットのMirror Registry for Red Hat OpenShift等の複数製品における信頼できないデータのデシリアライゼーションに関する脆弱性
Red Hat Quayの再開可能なコンテナイメージレイヤーアップロード処理に脆弱性が発見されました。アップロードプロセスは中間データをデータベースに保存しますが、その形式が改ざんされると、攻撃者がQuayサーバー上で任意のコードを実行できる可能性があります。
Operational remediation based on structured source evidence.
Status ?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 8 Apr 2026 · Last source change 9 Sept 2026, 22:38 UTC · CWE-502 · Deserialization of Untrusted Data
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source ?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-20515
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Affected versionsThe structured affected or fixed version information changed.
Before
See the vendor and CVE records for the affected range. · Fixed: mirror registry for Red Hat OpenShift 2.0: 1782177012 < *; Red Hat Quay 3.1: 1779822261 < *; Red Hat Quay 3.12: 1779811412 < *; Red Hat Quay 3.14: 1779689392 < *; Red Hat Quay 3.15: 1780891395 < *; Red Hat Quay 3.16: 1779204086 < *; Red Hat Quay 3.17: 1779922205 < *, 1780604033 < *; Red Hat Quay 3.18: 1784987273 < *; Red Hat Quay 3.9: 1779811473 < *
After
See the vendor and CVE records for the affected range. · Fixed: mirror registry for Red Hat OpenShift 2.0: 1782177012 < *; Red Hat Quay 3.10: 1779822261 < *; Red Hat Quay 3.12: 1779811412 < *; Red Hat Quay 3.14: 1779689392 < *; Red Hat Quay 3.15: 1780891395 < *; Red Hat Quay 3.16: 1779204086 < *; Red Hat Quay 3.17: 1779922205 < *, 1780604033 < *; Red Hat Quay 3.18: 1784987273 < *; Red Hat Quay 3.9: 1779811473 < *
Affected versionsThe structured affected or fixed version information changed.
Before
openshift/mirror-registry-rhel8 as a component of mirror registry for Red Hat OpenShift · Fixed: registry.redhat.io/quay/quay-rhel8@sha256:6e84443d520fc3f75352783c17e4262db596b6a7b194970f0cb276e52aa7cb26_arm64 as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:80c3d7a1c4b60d82101d6ab598498977fd7e5e6c3a82be0c44afec6fb84cb45a_ppc64le as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:c8de70845d1b044f955b1bcdab78ea997a665a9322b3fb8635602679292d8978_amd64 as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:f88e76824ab3d5d3b054bb79c33fc5bf8183238a8bf3e963d978437b0cfa2d69_s390x as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:4ae7d2d72a2370bd5401f570e21386bc9a6df0b145030060c922fcf754c7839b_s390x as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:9f5d146fc72a09d9067705a35274a251708cebc4c6a7e50615bdbce3e128c097_amd64 as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:a46c3fd8bb72616f07d2fb47eae9b060ea6c5135ec365d7ddc0dc18054da0b1b_arm64 as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:fca718bcd95971e571d13f9139e2f40c2daeca9605c669d73ed3055d9e3a53e2_ppc64le as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:5b1b98cd31ba150aecd6ef44c2bd8d79ae64380c8e974a4c8c1bb66fb4a38ce9_ppc64le as a component of Red Hat Quay 3.15; registry.redhat.io/quay/quay-rhel8@sha256:88ca55bb3177d8111971f1ba134bec7967289bfae64ecdf0b751dba0df82d9f0_s390x as a component of Red Hat Quay 3.15; registry.redhat.io/quay/quay-rhel8@sha256:afeeca0c1a653b5c375af4cca8dac1f52db846013d8b50e914ed62e1b7b1aa62_amd64 as a component of Red Hat Quay 3.15; registry.redhat.io/quay/quay-rhel9@sha256:139cae64e4790ebf8b760c6376a33d15233222a25e4da39c6062d7e46c3a1bef_amd64 as a component of Red Hat Quay 3.16; registry.redhat.io/quay/quay-rhel9@sha256:52883f389182907dec0e286d626c4faea0f4ae29a5d0e841d6ad2287fdb964c2_arm64 as a component of Red Hat Quay 3.16; registry.redhat.io/quay/quay-rhel9@sha256:ad162e6ea2f6fd246f605180699ce36e4ea91c4b551c7af600a64e671a303ee9_s390x as a component of Red Hat Quay 3.16; registry.redhat.io/quay/quay-rhel9@sha256:f6a15c2f1b4d5900cdbd366080e40d3a90d51ba9e5b4d6196e15eefe69d902c3_ppc64le as a component of Red Hat Quay 3.16; registry.redhat.io/quay/quay-rhel9@sha256:17c8a5b1140935b38cea1dcb846049a3901f3f7932990a83f65e0fdce015cf78_ppc64le as a component of Red Hat Quay 3.17; registry.redhat.io/quay/quay-rhel9@sha256:5ffa091bf9859a0ad3902c92c71d6387ac68e358e9794c86709879e3fac1bb0f_amd64 as a component of Red Hat Quay 3.17; registry.redhat.io/quay/quay-rhel9@sha256:65c631d107c264bef8a74336077b413609da4cfc37c8c9488afdcaa0df07dad5_s390x as a component of Red Hat Quay 3.17; registry.redhat.io/quay/quay-rhel9@sha256:8c7f4a453b3414c2d3457f2a8c65b67c70dd55e4bf7a31a9f3674865af5e1da1_amd64 as a component of Red Hat Quay 3.17; registry.redhat.io/quay/quay-rhel9@sha256:9e4588550a0e266f7598eb4af1dd020629357ffd305a02d8e7765114c7210812_ppc64le as a component of Red Hat Quay 3.17; registry.redhat.io/quay/quay-rhel9@sha256:a24c973edd52d4a418d415d54108cf44f495a969db1d0f6e5b6149e0a6021110_arm64 as a component of Red Hat Quay 3.17; registry.redhat.io/quay/quay-rhel9@sha256:a86a0e490321c469e791ad78ecdb3e42f33ab882602a5da50f9996d41c001ee7_arm64 as a component of Red Hat Quay 3.17; registry.redhat.io/quay/quay-rhel9@sha256:de281a104a00886f8f3afb43422d6f147547afb4526c339e95dc06ff92085de2_s390x as a component of Red Hat Quay 3.17; registry.redhat.io/quay/quay-rhel9@sha256:14e7fd727c1dc74e19001952176a8354cbc97ec5b4643a4815b6ffbc6d76e224_s390x as a component of Red Hat Quay 3.18; registry.redhat.io/quay/quay-rhel9@sha256:4207ba218f8ae31531add66d3ef5bf726f0034dfa7abb109d2c1bb1e2ed8b95b_ppc64le as a component of Red Hat Quay 3.18; registry.redhat.io/quay/quay-rhel9@sha256:6446f4989c8ad3d09abbd7ccf4af8ee341044f833b2d1e8d2c410c899dc1aa80_amd64 as a component of Red Hat Quay 3.18; registry.redhat.io/quay/quay-rhel9@sha256:9ee2985651443aef099fd421de5e9b7adb550aeafe2479a424864b85e0e50bc1_arm64 as a component of Red Hat Quay 3.18; registry.redhat.io/quay/quay-rhel8@sha256:5fda9676baf87c3bbcbf4cc37588b4d0f2c24f1be36fec0d90afe044f673c5dc_amd64 as a component of Red Hat Quay 3.1; registry.redhat.io/quay/quay-rhel8@sha256:a1c0a72df841fd97f7def41b3de85bfd7ceaa809805bebf3291ba54345bda7a1_s390x as a component of Red Hat Quay 3.1; registry.redhat.io/quay/quay-rhel8@sha256:c068b508acb9777d4cbacec4c6bd451b2858786ac4bfa249a1575f993efb7cb5_ppc64le as a component of Red Hat Quay 3.1; and 6 more
After
openshift/mirror-registry-rhel8 as a component of mirror registry for Red Hat OpenShift · Fixed: registry.redhat.io/quay/quay-rhel8@sha256:5fda9676baf87c3bbcbf4cc37588b4d0f2c24f1be36fec0d90afe044f673c5dc_amd64 as a component of Red Hat Quay 3.10; registry.redhat.io/quay/quay-rhel8@sha256:a1c0a72df841fd97f7def41b3de85bfd7ceaa809805bebf3291ba54345bda7a1_s390x as a component of Red Hat Quay 3.10; registry.redhat.io/quay/quay-rhel8@sha256:c068b508acb9777d4cbacec4c6bd451b2858786ac4bfa249a1575f993efb7cb5_ppc64le as a component of Red Hat Quay 3.10; registry.redhat.io/quay/quay-rhel8@sha256:6e84443d520fc3f75352783c17e4262db596b6a7b194970f0cb276e52aa7cb26_arm64 as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:80c3d7a1c4b60d82101d6ab598498977fd7e5e6c3a82be0c44afec6fb84cb45a_ppc64le as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:c8de70845d1b044f955b1bcdab78ea997a665a9322b3fb8635602679292d8978_amd64 as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:f88e76824ab3d5d3b054bb79c33fc5bf8183238a8bf3e963d978437b0cfa2d69_s390x as a component of Red Hat Quay 3.12; registry.redhat.io/quay/quay-rhel8@sha256:4ae7d2d72a2370bd5401f570e21386bc9a6df0b145030060c922fcf754c7839b_s390x as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:9f5d146fc72a09d9067705a35274a251708cebc4c6a7e50615bdbce3e128c097_amd64 as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:a46c3fd8bb72616f07d2fb47eae9b060ea6c5135ec365d7ddc0dc18054da0b1b_arm64 as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:fca718bcd95971e571d13f9139e2f40c2daeca9605c669d73ed3055d9e3a53e2_ppc64le as a component of Red Hat Quay 3.14; registry.redhat.io/quay/quay-rhel8@sha256:5b1b98cd31ba150aecd6ef44c2bd8d79ae64380c8e974a4c8c1bb66fb4a38ce9_ppc64le as a component of Red Hat Quay 3.15; registry.redhat.io/quay/quay-rhel8@sha256:88ca55bb3177d8111971f1ba134bec7967289bfae64ecdf0b751dba0df82d9f0_s390x as a component of Red Hat Quay 3.15; registry.redhat.io/quay/quay-rhel8@sha256:afeeca0c1a653b5c375af4cca8dac1f52db846013d8b50e914ed62e1b7b1aa62_amd64 as a component of Red Hat Quay 3.15; registry.redhat.io/quay/quay-rhel9@sha256:139cae64e4790ebf8b760c6376a33d15233222a25e4da39c6062d7e46c3a1bef_amd64 as a component of Red Hat Quay 3.16; registry.redhat.io/quay/quay-rhel9@sha256:52883f389182907dec0e286d626c4faea0f4ae29a5d0e841d6ad2287fdb964c2_arm64 as a component of Red Hat Quay 3.16; registry.redhat.io/quay/quay-rhel9@sha256:ad162e6ea2f6fd246f605180699ce36e4ea91c4b551c7af600a64e671a303ee9_s390x as a component of Red Hat Quay 3.16; registry.redhat.io/quay/quay-rhel9@sha256:f6a15c2f1b4d5900cdbd366080e40d3a90d51ba9e5b4d6196e15eefe69d902c3_ppc64le as a component of Red Hat Quay 3.16; registry.redhat.io/quay/quay-rhel9@sha256:17c8a5b1140935b38cea1dcb846049a3901f3f7932990a83f65e0fdce015cf78_ppc64le as a component of Red Hat Quay 3.17; registry.redhat.io/quay/quay-rhel9@sha256:5ffa091bf9859a0ad3902c92c71d6387ac68e358e9794c86709879e3fac1bb0f_amd64 as a component of Red Hat Quay 3.17; registry.redhat.io/quay/quay-rhel9@sha256:65c631d107c264bef8a74336077b413609da4cfc37c8c9488afdcaa0df07dad5_s390x as a component of Red Hat Quay 3.17; registry.redhat.io/quay/quay-rhel9@sha256:8c7f4a453b3414c2d3457f2a8c65b67c70dd55e4bf7a31a9f3674865af5e1da1_amd64 as a component of Red Hat Quay 3.17; registry.redhat.io/quay/quay-rhel9@sha256:9e4588550a0e266f7598eb4af1dd020629357ffd305a02d8e7765114c7210812_ppc64le as a component of Red Hat Quay 3.17; registry.redhat.io/quay/quay-rhel9@sha256:a24c973edd52d4a418d415d54108cf44f495a969db1d0f6e5b6149e0a6021110_arm64 as a component of Red Hat Quay 3.17; registry.redhat.io/quay/quay-rhel9@sha256:a86a0e490321c469e791ad78ecdb3e42f33ab882602a5da50f9996d41c001ee7_arm64 as a component of Red Hat Quay 3.17; registry.redhat.io/quay/quay-rhel9@sha256:de281a104a00886f8f3afb43422d6f147547afb4526c339e95dc06ff92085de2_s390x as a component of Red Hat Quay 3.17; registry.redhat.io/quay/quay-rhel9@sha256:14e7fd727c1dc74e19001952176a8354cbc97ec5b4643a4815b6ffbc6d76e224_s390x as a component of Red Hat Quay 3.18; registry.redhat.io/quay/quay-rhel9@sha256:4207ba218f8ae31531add66d3ef5bf726f0034dfa7abb109d2c1bb1e2ed8b95b_ppc64le as a component of Red Hat Quay 3.18; registry.redhat.io/quay/quay-rhel9@sha256:6446f4989c8ad3d09abbd7ccf4af8ee341044f833b2d1e8d2c410c899dc1aa80_amd64 as a component of Red Hat Quay 3.18; registry.redhat.io/quay/quay-rhel9@sha256:9ee2985651443aef099fd421de5e9b7adb550aeafe2479a424864b85e0e50bc1_arm64 as a component of Red Hat Quay 3.18; and 6 more
Affected versionsThe structured affected or fixed version information changed.
Before
See the vendor and CVE records for the affected range. · Fixed: 1782177012 < *; 1779822261 < *; 1779811412 < *; 1779689392 < *; 1780891395 < *; 1779204086 < *; 1779922205 < *; 1780604033 < *
After
See the vendor and CVE records for the affected range. · Fixed: mirror registry for Red Hat OpenShift 2.0: 1782177012 < *; Red Hat Quay 3.1: 1779822261 < *; Red Hat Quay 3.12: 1779811412 < *; Red Hat Quay 3.14: 1779689392 < *; Red Hat Quay 3.15: 1780891395 < *; Red Hat Quay 3.16: 1779204086 < *; Red Hat Quay 3.17: 1779922205 < *, 1780604033 < *; Red Hat Quay 3.18: 1784987273 < *; Red Hat Quay 3.9: 1779811473 < *
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.