{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-15927 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-15927 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-15927 is a medium-severity server-side request forgery vulnerability in Red Hat Quay 3.10, published on 21 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-15927 and fix it if it is affected.\n\nWhat it is: CVE-2026-15927 is a medium-severity server-side request forgery vulnerability in Red Hat Quay 3.10, published on 21 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-15927 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-15927/ (Markdown: https://insights.sbomify.com/CVE-2026-15927/index.md)","id":"CVE-2026-15927","markdown":"https://insights.sbomify.com/CVE-2026-15927/index.md","name":"CVE-2026-15927","record":{"aliases":["GHSA-9rpm-rwwc-xw43"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Red Hat Quay","requires_auth":"high_privilege","summary":"Repository administrators can exploit missing URL validation in Quay's mirror configuration to perform Server-Side Request Forgery against internal services.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"A flaw was found in Red Hat Quay's repository-level mirror configuration\nfeature. The POST and PUT handlers in endpoints/api/mirror.py accept an\nexternal_reference parameter without SSRF validation, unlike the\norganization-level mirror handlers which apply validate_external_registry_url().\nA repository administrator can supply a crafted hostname that causes the Quay\nmirror worker to make requests via Skopeo to internal network services, cloud\nmetadata endpoints, or other resources not intended to be reachable from the\nQuay application.","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":"Quay: mirror-registry: ssrf: repo-level mirror accepts external_reference without url validation","id":"CVE-2026-15927","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":9,"next":{"headline":"Cross-site scripting in XMLRPC-C","id":"CVE-2026-15928"},"packages":[],"prev":{"headline":"Red Hat Product Security has determined that this CVE ID is not needed","id":"CVE-2026-15926"},"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.9","mirror registry for Red Hat OpenShift 2"],"published":"2026-07-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-09-22","vendors":["Red Hat"]},"summary":"Repository administrators can exploit missing URL validation in Quay's mirror configuration to perform Server-Side Request Forgery against internal services.","url":"https://insights.sbomify.com/CVE-2026-15927/"}