{"answers":{"affected":"4 open source packages ship an affected version, including zotregistry.dev/zot/v2 and zotregistry.dev/zot.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61833 exists.","fix":"Upgrade zotregistry.dev/zot/v2 to 2.1.18 or later.","what":"CVE-2026-61833 is a high-severity missing authorization vulnerability in project-zot zot, published on 18 Sep 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-61833 and fix it if it is affected.\n\nWhat it is: CVE-2026-61833 is a high-severity missing authorization vulnerability in project-zot zot, published on 18 Sep 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-61833 exists.\n\nAffected packages and fixed versions:\n- zotregistry.dev/zot/v2 (Go): affected all versions; fixed in 2.1.18\n- zotregistry.dev/zot/v2 (Go): affected all versions; fixed in 2.1.18\n- zotregistry.dev/zot/v2 (Go): affected all versions; fixed in 2.1.18\n- zotregistry.dev/zot (Go): affected all versions; no fix listed\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-61833/ (Markdown: https://insights.sbomify.com/CVE-2026-61833/index.md)","id":"CVE-2026-61833","markdown":"https://insights.sbomify.com/CVE-2026-61833/index.md","name":"CVE-2026-61833","record":{"aliases":["GHSA-qg67-7m6v-qg25","GO-2026-6527","MINI-24rp-p87c-g986","MINI-hjcm-p955-xp3v"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Container image registry","requires_auth":"low_privilege","summary":"Attackers with pull/push tokens can delete manifests and blobs due to incorrect scope mapping, causing data loss and service disruption.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"zot is a container image and artifact registry based on the Open Container Initiative Distribution Specification. Prior to 2.1.18, the bearer authentication handler in pkg/api/authn.go maps every HTTP method other than GET and HEAD to the push action, so DELETE requests are not checked for the distinct delete permission. Bearer-authenticated requests also bypass the fine-grained DistSpecAuthzHandler path in pkg/api/authz.go, while DeleteManifest and DeleteBlob perform no independent delete-permission check. A remote attacker with a bearer token limited to pull and push actions can therefore delete manifests and blobs within the token's repository scope, making images unavailable and allowing repository history to be altered despite the token lacking delete authorization. This issue is fixed in version 2.1.18.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"zot: Bearer authentication maps DELETE to push scope, allowing unauthorized deletion","id":"CVE-2026-61833","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":4,"n_references":4,"next":{"headline":"scim-patch: Mutation of Inherited Built-in Method Objects","id":"CVE-2026-61834"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"zotregistry.dev/zot","purl":"pkg:golang/zotregistry.dev/zot","source":"GO-2026-6527"},{"ecosystem":"Go","fixed":["2.1.18"],"introduced":["0"],"last_affected":[],"package":"zotregistry.dev/zot/v2","purl":null,"source":"GHSA-qg67-7m6v-qg25"},{"ecosystem":"Go","fixed":["2.1.18"],"introduced":["0"],"last_affected":[],"package":"zotregistry.dev/zot/v2","purl":"pkg:golang/zotregistry.dev/zot/v2","source":"GHSA-qg67-7m6v-qg25"},{"ecosystem":"Go","fixed":["2.1.18"],"introduced":["0"],"last_affected":[],"package":"zotregistry.dev/zot/v2","purl":"pkg:golang/zotregistry.dev/zot/v2","source":"GO-2026-6527"}],"prev":{"headline":"Auth bypass in nixpkgs","id":"CVE-2026-61828"},"products":["zot"],"published":"2026-09-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"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-09-23","vendors":["project-zot"]},"summary":"Attackers with pull/push tokens can delete manifests and blobs due to incorrect scope mapping, causing data loss and service disruption.","url":"https://insights.sbomify.com/CVE-2026-61833/"}