# CVE-2026-31801: zot create-only policy allows overwrite attempts of existing latest tag (update permission not required)

> Attackers with create permissions can overwrite existing 'latest' tags in zot registry without update permissions, bypassing authorization controls.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N`)
- **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:** 10 Mar 2026
- **Updated:** 11 Mar 2026
- **Also known as:** GHSA-85jx-fm8m-x8c6, GO-2026-4668

## What is CVE-2026-31801?

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

### Official description

zot is ancontainer image/artifact registry based on the Open Container Initiative Distribution Specification. From 1.3.0 to 2.1.14, zot’s dist-spec authorization middleware infers the required action for PUT /v2/{name}/manifests/{reference} as create by default, and only switches to update when the tag already exists and reference != "latest". As a result, when latest already exists, a user who is allowed to create (but not allowed to update) can still pass the authorization check for an overwrite attempt of latest. This vulnerability is fixed in 2.1.15.

Weakness: CWE-863 (Incorrect Authorization)

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

6 open source packages ship an affected version, including zotregistry.dev/zot and zotregistry.dev/zot/v2. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `zotregistry.dev/zot` | Go | All versions | None |
| `zotregistry.dev/zot` | Go | From 1.3.0-20210831063041-c8779d9e87d9 to 1.4.4-20251014054906-73eef25681af | None |
| `zotregistry.dev/zot` | Go | From 1.3.0-20210831063041-c8779d9e87d9 to 1.4.4-20251014054906-73eef25681af | None |
| `zotregistry.dev/zot/v2` | Go | All versions | 2.1.15 |
| `zotregistry.dev/zot/v2` | Go | All versions | 2.1.15 |
| `zotregistry.dev/zot/v2` | Go | All versions | 2.1.15 |

Products: Zotregistry Zot.

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

Upgrade to a fixed version.

## Is CVE-2026-31801 being exploited?

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

## Other vulnerabilities in project-zot zot

- [CVE-2025-23208](https://insights.sbomify.com/CVE-2025-23208/): IdP group membership revocation ignored in zot (high 7.3)
- [CVE-2024-39897](https://insights.sbomify.com/CVE-2024-39897/): Cache driver GetBlob() allows read access to any blob without access control check (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-31801 is a high-severity missing authorization vulnerability in project-zot zot, published on 10 Mar 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-31801 exists.

Affected packages and fixed versions:
- zotregistry.dev/zot (Go): affected all versions; no fix listed
- zotregistry.dev/zot (Go): affected from 1.3.0-20210831063041-c8779d9e87d9 up to 1.4.4-20251014054906-73eef25681af; no fix listed
- zotregistry.dev/zot (Go): affected from 1.3.0-20210831063041-c8779d9e87d9 up to 1.4.4-20251014054906-73eef25681af; no fix listed
- zotregistry.dev/zot/v2 (Go): affected all versions; fixed in 2.1.15
- zotregistry.dev/zot/v2 (Go): affected all versions; fixed in 2.1.15
- zotregistry.dev/zot/v2 (Go): affected all versions; fixed in 2.1.15

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-31801/ (Markdown: https://insights.sbomify.com/CVE-2026-31801/index.md)
```

## Sources

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

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