{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2376 exists.","fix":"No fix has been published for CVE-2026-2376 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-2376 is a medium-severity server-side request forgery vulnerability in Red Hat Quay 3, published on 12 Mar 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-2376 and fix it if it is affected.\n\nWhat it is: CVE-2026-2376 is a medium-severity server-side request forgery vulnerability in Red Hat Quay 3, published on 12 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2376 exists.\n\nAffected product: 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-2026-2376/ (Markdown: https://insights.sbomify.com/CVE-2026-2376/index.md)","id":"CVE-2026-2376","markdown":"https://insights.sbomify.com/CVE-2026-2376/index.md","name":"CVE-2026-2376","record":{"aliases":["GHSA-9w78-x9jw-9c7m"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Red Hat Quay","requires_auth":"low_privilege","summary":"An authenticated user can exploit an open redirect to force the server to access internal or restricted systems, enabling server-side request forgery.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"mirror_registry","vendor":"redhat"},{"product":"quay","vendor":"redhat"}],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"description":"A flaw was found in mirror-registry where an authenticated user can trick the system into accessing unintended internal or restricted systems by providing malicious web addresses. \n\nWhen the application processes these addresses, it automatically follows redirects without verifying the final destination, allowing attackers to route requests to systems they should not have access to.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Mirror-registry: quay: quay: server-side request forgery via open redirect vulnerability in web interface","id":"CVE-2026-2376","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Mirror-registry: quay: quay: server-side request forgery via log export functionality","id":"CVE-2026-2377"},"packages":[],"prev":{"headline":"Privilege escalation in App Builder – Create Native Android \u0026 iOS Apps On The Flight","id":"CVE-2026-2375"},"products":["Red Hat Quay 3","mirror registry for Red Hat OpenShift","mirror registry for Red Hat OpenShift 2"],"published":"2026-03-12","related":[{"cvss_score":8.8,"headline":"Mirror-registry: plain-text default csrf secret key","id":"CVE-2024-3622","kev_date_added":null,"published":"2024-04-25"},{"cvss_score":6.5,"headline":"Mirror-registry: default database secret key stored in plain-text on initial configuration file","id":"CVE-2024-3623","kev_date_added":null,"published":"2024-04-25"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-12","vendors":["Red Hat"]},"summary":"An authenticated user can exploit an open redirect to force the server to access internal or restricted systems, enabling server-side request forgery.","url":"https://insights.sbomify.com/CVE-2026-2376/"}