Vulnerability 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.
CVSS Score
HIGH
Related Weaknesses (CWE)
References
- https://github.com/project-zot/zot/commit/7bb211bcd4352b90f3e99752607fbd1f050bf7
- https://github.com/project-zot/zot/pull/4161
- https://github.com/project-zot/zot/releases/tag/v2.1.18
- https://github.com/project-zot/zot/security/advisories/GHSA-qg67-7m6v-qg25
FAQ
What is CVE-2026-61833?
CVE-2026-61833 is a vulnerability with a CVSS score of 8.1 (HIGH). 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...
How severe is CVE-2026-61833?
CVE-2026-61833 has been rated HIGH with a CVSS base score of 8.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-61833?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.