{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-105447 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-105447 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-105447 is a medium-severity missing authorization vulnerability in Red Hat Quay 3, published on 5 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-105447 and fix it if it is affected.\n\nWhat it is: CVE-2026-105447 is a medium-severity missing authorization vulnerability in Red Hat Quay 3, published on 5 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-105447 in the wild and no public exploit code.\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-105447/ (Markdown: https://insights.sbomify.com/CVE-2026-105447/index.md)","id":"CVE-2026-105447","markdown":"https://insights.sbomify.com/CVE-2026-105447/index.md","name":"CVE-2026-105447","record":{"aliases":["GHSA-wr22-68gv-32xw"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Container registry","requires_auth":"high_privilege","summary":"Read-only admins can retrieve write tokens via build trigger API, allowing unauthorized image pushes to private repositories.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"A flaw was found in Quay. When handling build trigger requests, the application incorrectly exposes trigger configuration details containing repository write tokens to global read-only administrative users. An authenticated user with read-only privileges can exploit this flaw by querying the build trigger API to retrieve these delegate tokens. This issue allows a restricted user to bypass read-only limitations and push arbitrary container images to private repositories, leading to privilege escalation.","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: quay: global read-only superuser can access build trigger write credentials","id":"CVE-2026-105447","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Docker Sandboxes egress proxy could forward unrecognized client credentials to managed hosts","id":"CVE-2026-105452"},"packages":[],"prev":{"headline":"Docker Hub account conversion could reassign an active personal access token to another user","id":"CVE-2026-105445"},"products":["Red Hat Quay 3"],"published":"2026-10-05","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-10-08","vendors":["Red Hat"]},"summary":"Read-only admins can retrieve write tokens via build trigger API, allowing unauthorized image pushes to private repositories.","url":"https://insights.sbomify.com/CVE-2026-105447/"}