CVE-2026-61833 zot: Bearer authentication maps DELETE to push scope, allowing unauthorized deletion
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- Proof of concept public · automatable: no · technical impact: partial
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.
Upgrade path
2 packages: 0 fixed, 1 partially fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| zotregistry.dev/zot(Go) | < 2.1.18; All versions | 2.1.18 | Partially fixed |
| project-zot zot | = < 2.1.18 | No fix listed | Versions listed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| zotregistry.dev/zot(Go) | < 2.1.18 | 2.1.18 |
| zotregistry.dev/zot(Go) | All versions | No fix listed |
| project-zot zot | = < 2.1.18 | No fix listed |
References
- https://github.com/project-zot/zot/security/advisories/GHSA-qg67-7m6v-qg25 exploit vendor-advisory
- https://github.com/project-zot/zot/pull/4161 patch
- https://github.com/project-zot/zot/commit/7bb211bcd4352b90f3e99752607fbd1f050bf7ca patch
- github.com product
- https://github.com/project-zot/zot/releases/tag/v2.1.18
- github.com