CVE-2026-61833: zot: Bearer authentication maps DELETE to push scope, allowing unauthorized deletion
A bearer token with only pull and push scopes can successfully delete manifests and blobs from a zot registry. The bearer authentication handler maps all non-GET/HEAD HTTP methods, including DELETE, to the "push" action, and the DistSpecAuthzHandler middleware is bypassed entirely for bearer-authenticated requests. This allows any client holding a push-only bearer token to delete arbitrary manifests and blobs within the token’s repository scope, in violation of the Docker Distribution Token Authentication Specification.
References
- github.com/advisories/GHSA-qg67-7m6v-qg25
- github.com/project-zot/zot/commit/7bb211bcd4352b90f3e99752607fbd1f050bf7ca
- github.com/project-zot/zot/pull/4161
- github.com/project-zot/zot/releases/tag/v2.1.18
- github.com/project-zot/zot/security/advisories/GHSA-qg67-7m6v-qg25
- nvd.nist.gov/vuln/detail/CVE-2026-61833
Code Behaviors & Features
Detect and mitigate CVE-2026-61833 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →