CVE-2026-61833

High

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.

SeverityHigh
CVSS8.1
Exploit probability—
ProductZotregistry.dev/zot/v2
PublishedSep 18, 2026
First seenSep 18, 2026
Weakness typeCWE-285CWE-285

How to fix

Update
  • zotregistry.dev/zot/v22.1.18 or later

Affected products

ProductAffected versionsFixed in
zotregistry.dev/zot/v2Gov < 2.1.182.1.18
zotregistry.dev/zotGoNo range specified—

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.