CVE-2026-61833 PUBLISHED

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

Assigner: GitHub_M
Reserved: 10.07.2026 Published: 18.09.2026 Updated: 18.09.2026

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.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
CVSS Score: 8.1

Product Status

Vendor project-zot
Product zot
Versions
  • Version < 2.1.18 is affected

References

Problem Types

  • CWE-285: Improper Authorization CWE