| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-qg67-7m6v-qg25 | zot: Bearer authentication maps DELETE to push scope, allowing unauthorized deletion |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 25 Sep 2026 05:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Sun, 20 Sep 2026 04:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Project-zot
Project-zot zot |
|
| Vendors & Products |
Project-zot
Project-zot zot |
Fri, 18 Sep 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | zot: Bearer authentication maps DELETE to push scope, allowing unauthorized deletion | |
| Weaknesses | CWE-285 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-09-23T19:06:14.333Z
Reserved: 2026-07-10T20:28:17.511Z
Link: CVE-2026-61833
Updated: 2026-09-23T19:05:52.607Z
Status : Deferred
Published: 2026-09-18T17:16:59.010
Modified: 2026-09-30T17:32:07.107
Link: CVE-2026-61833
No data.
OpenCVE Enrichment
Updated: 2026-09-20T04:15:17Z
Github GHSA