{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-123710 in the wild and no public exploit code.","exposure":"An affected version is exposed as installed. No special setting or call is needed.","fix":"No fix has been published for CVE-2026-123710 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-123710 is a critical authentication bypass vulnerability in Red Hat Quay 3.10, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-123710 and fix it if it is affected.\n\nWhat it is: CVE-2026-123710 is a critical authentication bypass vulnerability in Red Hat Quay 3.10, published on 11 Nov 2026. 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-2026-123710 in the wild and no public exploit code.\nExposure: An affected version is exposed as installed. No special setting or call is needed.\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-123710/ (Markdown: https://insights.sbomify.com/CVE-2026-123710/index.md)","id":"CVE-2026-123710","markdown":"https://insights.sbomify.com/CVE-2026-123710/index.md","name":"CVE-2026-123710","record":{"aliases":["GHSA-jw94-v4wp-236w"],"analysis":{"component_type":"container_or_infrastructure","exploitable_when_present":false,"fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"container registry","requires_auth":"none","requires_specific_call":false,"summary":"Unauthenticated clients can obtain a long-lived anonymous registry token and install a permanent signing key, gaining read/write access to private Quay images.","user_interaction":"not_required","vuln_class":"auth_bypass","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"redhat","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-1287","name":"Improper Validation of Specified Type of Input"}],"description":"A flaw was found in Red Hat Quay. An unauthenticated client can obtain an anonymous registry token with an audience it controls, present that token to the service key rotation endpoint, and install its own approved signing key with no expiry. Registry tokens signed with that key are accepted for any repository, allowing read and write access to private images and replacement of repository tags.","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: red hat quay: unauthenticated registry signing-key takeover via service key rotation","id":"CVE-2026-123710","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":11,"next":{"headline":"[Eclipse CSI - otterdog] OS Command Injection and Arbitrary Code Execution","id":"CVE-2026-123717"},"nickname":null,"packages":[],"prev":{"headline":"Security For WooCommerce \u003c= 1.0.16 - Unauthenticated Server Configuration Information Disclosure","id":"CVE-2026-123705"},"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","Red Hat Quay 5"],"published":"2026-11-11","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-11-12","vendors":["Red Hat"]},"summary":"Unauthenticated clients can obtain a long-lived anonymous registry token and install a permanent signing key, gaining read/write access to private Quay images.","url":"https://insights.sbomify.com/CVE-2026-123710/"}