{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-4374 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-4374 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-4374 is a medium-severity vulnerability in Project Quay Red Hat Quay 3, published on 6 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-4374 and fix it if it is affected.\n\nWhat it is: CVE-2025-4374 is a medium-severity vulnerability in Project Quay Red Hat Quay 3, published on 6 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-4374 in the wild and no public exploit code.\n\nAffected product: Project Quay Red Hat Quay 3. 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-2025-4374/ (Markdown: https://insights.sbomify.com/CVE-2025-4374/index.md)","id":"CVE-2025-4374","markdown":"https://insights.sbomify.com/CVE-2025-4374/index.md","name":"CVE-2025-4374","record":{"aliases":["GHSA-f5vq-pq35-3qqc"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"Container registry","requires_auth":"none","summary":"Attackers can gain Admin permissions on newly created repositories when pulling uncached images in proxy cache mode.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"quay","vendor":"redhat"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-266","name":"Incorrect Privilege Assignment"}],"description":"A flaw was found in Quay. When an organization acts as a proxy cache, and a user or robot pulls an image that hasn't been mirrored yet, they are granted \"Admin\" permissions on the newly created repository.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Quay: incorrect privilege assignment","id":"CVE-2025-4374","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2025"},"n_packages":0,"n_references":6,"next":{"headline":"Cross-Site Request Forgery vulnerability in Pro Cloud Server's WebEA","id":"CVE-2025-4375"},"packages":[],"prev":{"headline":"Glib: buffer underflow on glib through glib/gstring.c via function g_string_insert_unichar","id":"CVE-2025-4373"},"products":["Red Hat Quay 3","quay"],"published":"2025-05-06","related":[{"cvss_score":9,"headline":"Cross-site scripting in quay","id":"CVE-2020-27832","kev_date_added":null,"published":"2021-05-27"},{"cvss_score":6.5,"headline":"Quay: clickjacking on config-editor page severity","id":"CVE-2023-4956","kev_date_added":null,"published":"2023-11-07"},{"cvss_score":6.5,"headline":"Quay: cross-site request forgery (csrf) on config-editor page","id":"CVE-2023-4959","kev_date_added":null,"published":"2023-09-15"},{"cvss_score":6,"headline":"Information disclosure in quay","id":"CVE-2019-10205","kev_date_added":null,"published":"2020-01-02"},{"cvss_score":5.4,"headline":"Quay: red hat quay: authentication bypass allows privileged actions without valid credentials","id":"CVE-2026-6848","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":5.4,"headline":"Quay: stored cross site scripting","id":"CVE-2023-3384","kev_date_added":null,"published":"2023-07-24"}],"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":"partial"},"state":"PUBLISHED","updated":"2026-08-07","vendors":["Project Quay","Red Hat"]},"summary":"Attackers can gain Admin permissions on newly created repositories when pulling uncached images in proxy cache mode.","url":"https://insights.sbomify.com/CVE-2025-4374/"}