# zot’s create-only policy allows overwrite attempts of existing latest tag (update permission not required)

Advisory record · `GHSA-85jx-fm8m-x8c6`

- **Identifiers:** `GHSA-85jx-fm8m-x8c6` · `CVE-2026-31801` · `GO-2026-4668`
- **State:** Confirmed
- **Severity:** CVSS 7.7 High
- **Critical:** No
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 10 Mar 2026
- **Updated:** 23 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 10 Mar 2026, 23:44 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `zotregistry.dev/zot/v2` (Go): affected `<2.1.15`; fixed in `2.1.15`
- `zotregistry.dev/zot` (Go): affected `>=1.3.0-20210831063041-c8779d9e87d9, <=1.4.4-20251014054906-73eef25681af`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Zot (zotregistry.dev/zot/v2) before 2.1.15 has an authorization flaw in which a user with create permission but without update permission can overwrite an existing \`latest\` tag through a manifest push. An attacker needs an account with create-only access to a repository that already has a \`latest\` tag, and can then change that tag's digest. Upgrade to zotregistry.dev/zot/v2 version 2.1.15 or later. The package zotregistry.dev/zot has no fixed version listed.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.7 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0024, the 15th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:09 UTC: First seen by agentprime
- 31 Oct 2026, 15:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-85jx-fm8m-x8c6)

## Sources

- [GitHub Advisory Database: GHSA-85jx-fm8m-x8c6](https://github.com/advisories/GHSA-85jx-fm8m-x8c6)
- [OSV: GHSA-85jx-fm8m-x8c6](https://osv.dev/vulnerability/GHSA-85jx-fm8m-x8c6)
- <https://github.com/project-zot/zot/security/advisories/GHSA-85jx-fm8m-x8c6>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-31801>
- <https://github.com/project-zot/zot>
- <https://github.com/project-zot/zot/releases/tag/v2.1.15>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-85jx-fm8m-x8c6>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-85jx-fm8m-x8c6/>. Everything for agents: <https://agentprime.io/llms.txt>.
