# CVE-2026-61833: zot: Bearer authentication maps DELETE to push scope, allowing unauthorized deletion

> Attackers with pull/push tokens can delete manifests and blobs due to incorrect scope mapping, causing data loss and service disruption.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-qg67-7m6v-qg25, GO-2026-6527, MINI-24rp-p87c-g986, MINI-hjcm-p955-xp3v

## What is CVE-2026-61833?

CVE-2026-61833 is a high-severity missing authorization vulnerability in project-zot zot, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-61833?

4 open source packages ship an affected version, including zotregistry.dev/zot/v2 and zotregistry.dev/zot.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `zotregistry.dev/zot/v2` | Go | All versions | 2.1.18 |
| `zotregistry.dev/zot/v2` | Go | All versions | 2.1.18 |
| `zotregistry.dev/zot/v2` | Go | All versions | 2.1.18 |
| `zotregistry.dev/zot` | Go | All versions | None |

## How do I fix CVE-2026-61833?

Upgrade zotregistry.dev/zot/v2 to 2.1.18 or later.

## Is CVE-2026-61833 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61833 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61833 and fix it if it is affected.

What it is: CVE-2026-61833 is a high-severity missing authorization vulnerability in project-zot zot, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61833 exists.

Affected packages and fixed versions:
- zotregistry.dev/zot/v2 (Go): affected all versions; fixed in 2.1.18
- zotregistry.dev/zot/v2 (Go): affected all versions; fixed in 2.1.18
- zotregistry.dev/zot/v2 (Go): affected all versions; fixed in 2.1.18
- zotregistry.dev/zot (Go): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-61833/ (Markdown: https://insights.sbomify.com/CVE-2026-61833/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-61833
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-61833
- OSV: https://osv.dev/vulnerability/CVE-2026-61833

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-61833/
Summaries are generated and may contain mistakes; the official description above is the record.