CVE-2026-61833

published 18 Sep 2026 · updated 23 Sep 2026

zot: Bearer authentication maps DELETE to push scope, allowing unauthorized deletion

8.1HighCVSS 8.1EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
project-zot<2.1.18

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-61833 severity on Zeptric[![CVE-2026-61833](https://zeptric.io/badge/cve/CVE-2026-61833.svg)](https://zeptric.io/cve/CVE-2026-61833)