CVE-2026-31801 json
zot create-only policy allows overwrite attempts of existing latest tag (update permission not required)
published 7mo ago modified 4mo ago also EUVD-2026-10890 , GHSA-85jx-fm8m-x8c6 , GO-2026-4668
- cvss
- 7.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go zotregistry.dev/zot/v2 2.1.15
- zotregistry zot 2.1.15
- govulncheck-vulndb openSUSE Leap 15.6 0.0.20260317T205859-150000.1.152.1
suse advisories SUSE-SU-2026:1042-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
Is CVE-2026-31801 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7mo ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/project-zot/zot/security/advisories/GHSA-85jx-fm8m-x8c6 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N |
| GitHub | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | zotregistry.dev/zot/v2 | <2.1.15 |
2.1.15 |
| go | zotregistry.dev/zot | >=1.3.0-20210831063041-c8779d9e87d9, <=1.4.4-20251014054906-73eef25681af all versions |
no fix listed |
Affected products
- project-zot zot
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
github.com
/project-zot/zot/security/advisories/GHSA-85jx-fm8m-x8c6
web, exploit, mitigation, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-31801
advisory
-
github.com
/project-zot/zot
package
-
github.com
/project-zot/zot/releases/tag/v2.1.15
web
Sources
- CVE List CVE-2026-31801
- GitHub Advisory GHSA-85jx-fm8m-x8c6
- NVD CVE-2026-31801
- OSV GO-2026-4668
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.