{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2026-32590 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-32590 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32590 is a high-severity unsafe deserialization vulnerability in Red Hat Quay 3.10, published on 8 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-32590 and fix it if it is affected.\n\nWhat it is: CVE-2026-32590 is a high-severity unsafe deserialization vulnerability in Red Hat Quay 3.10, published on 8 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-32590 in the wild and no public exploit code.\n\nAffected product: Red Hat Quay 3.10. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-32590/ (Markdown: https://insights.sbomify.com/CVE-2026-32590/index.md)","id":"CVE-2026-32590","markdown":"https://insights.sbomify.com/CVE-2026-32590/index.md","name":"CVE-2026-32590","record":{"aliases":["GHSA-mvqc-wfv6-7764"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Red Hat Quay","requires_auth":"low_privilege","summary":"An attacker can execute arbitrary code on the Red Hat Quay server by tampering with intermediate data during resumable container image layer uploads.","user_interaction":"required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"mirror_registry_for_red_hat_openshift","vendor":"redhat"},{"product":"quay","vendor":"redhat"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Mirror-registry: remote code execution using pickle deserialization","id":"CVE-2026-32590","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2026"},"n_packages":0,"n_references":12,"next":{"headline":"Mirror-registry: quay: server-side request forgery in proxy cache upstream registry configuration","id":"CVE-2026-32591"},"packages":[],"prev":{"headline":"Mirror-registry: quay: insecure direct object reference in blobupload","id":"CVE-2026-32589"},"products":["Red Hat Quay 3.10","Red Hat Quay 3.12","Red Hat Quay 3.14","Red Hat Quay 3.15","Red Hat Quay 3.16","Red Hat Quay 3.17","Red Hat Quay 3.18","Red Hat Quay 3.9","mirror registry for Red Hat OpenShift","mirror registry for Red Hat OpenShift 2.0"],"published":"2026-04-08","related":[{"cvss_score":7.4,"headline":"Mirror-registry: quay: insecure direct object reference in blobupload","id":"CVE-2026-32589","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":6.5,"headline":"Mirror-registry: quay: quay: server-side request forgery via log export functionality","id":"CVE-2026-2377","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":5.3,"headline":"Mirror-registry: openshift mirror registry: user enumeration via authentication error messages","id":"CVE-2025-14243","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":5.2,"headline":"Mirror-registry: quay: server-side request forgery in proxy cache upstream registry configuration","id":"CVE-2026-32591","kev_date_added":null,"published":"2026-04-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-09","vendors":["Red Hat"]},"summary":"An attacker can execute arbitrary code on the Red Hat Quay server by tampering with intermediate data during resumable container image layer uploads.","url":"https://insights.sbomify.com/CVE-2026-32590/"}