{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2026-2377 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-2377 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-2377 is a medium-severity server-side request forgery vulnerability in Red Hat Quay 3.10, published on 8 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-2377 and fix it if it is affected.\n\nWhat it is: CVE-2026-2377 is a medium-severity server-side request forgery vulnerability in Red Hat Quay 3.10, published on 8 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-2377 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-2377/ (Markdown: https://insights.sbomify.com/CVE-2026-2377/index.md)","id":"CVE-2026-2377","markdown":"https://insights.sbomify.com/CVE-2026-2377/index.md","name":"CVE-2026-2377","record":{"aliases":["GHSA-2c4x-699h-vw5x"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Red Hat Quay","requires_auth":"low_privilege","summary":"An authenticated attacker can exploit the log export feature to perform server-side request forgery, potentially disclosing sensitive internal network information.","user_interaction":"not_required","vuln_class":"ssrf"},"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":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 and mirror registry for Red Hat OpenShift. The log export feature in these products allows an authenticated user to specify an arbitrary callback URL. A backend process then makes server-side HTTP requests to this provided URL. This vulnerability, known as Server-Side Request Forgery (SSRF), could allow an attacker to send requests from the application's internal network, potentially leading to the disclosure of sensitive information.","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: quay: quay: server-side request forgery via log export functionality","id":"CVE-2026-2377","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Address bar spoofing risk in ArcSearch on Android","id":"CVE-2026-2378"},"packages":[],"prev":{"headline":"Mirror-registry: quay: quay: server-side request forgery via open redirect vulnerability in web interface","id":"CVE-2026-2376"},"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.9","mirror registry for Red Hat OpenShift","mirror registry for Red Hat OpenShift 2"],"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":7.1,"headline":"Mirror-registry: remote code execution using pickle deserialization","id":"CVE-2026-32590","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":"partial"},"state":"PUBLISHED","updated":"2026-09-10","vendors":["Red Hat"]},"summary":"An authenticated attacker can exploit the log export feature to perform server-side request forgery, potentially disclosing sensitive internal network information.","url":"https://insights.sbomify.com/CVE-2026-2377/"}