Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.7

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

CVE-2026-31801GHSA-85jx-fm8m-x8c6

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go zotregistry.dev/zot/v2

    Affected
    < 2.1.15
    Fixed in
    2.1.15

  • Go zotregistry.dev/zot

    Affected
    >= 1.3.0-20210831063041-c8779d9e87d9, <= 1.4.4-20251014054906-73eef25681af
    Fixed in
    no fixed version recorded

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-85jx-fm8m-x8c6 lists affected ranges: Go zotregistry.dev/zot/v2 >=0 =1.3.0-20210831063041-c8779d9e87d9 <=1.4.4-20251014054906-73eef25681af

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
EPSS
  • CVE-2026-31801: 0.22% estimated exploitation activity in the next 30 days; percentile 12.73 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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. affected component - file: pkg/api/authz.go (DistSpecAuthzHandler) - condition: slices.Contains(tags, reference) && reference != "latest" (line 352 at the pinned commit) severity HIGH category: CWE-863 (incorrect authorization) note: impact depends on how a deployment uses latest (for example, if latest is treated as a protected or “push-once” tag), and on how access control is provisioned (users with create but without update). the attached poc demonstrates a real overwrite of latest (tag digest changes) under a create-only policy. steps to reproduce 1. configure access control so user attacker has…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-85jx-fm8m-x8c6

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-31801

Advisory: zot’s create-only policy allows overwrite attempts of existing latest tag (update permission not required)
IDs: CVE-2026-31801, GHSA-85jx-fm8m-x8c6
Record: https://patchnext.com/advisories/cve-2026-31801 (revision 1, source checked 26 Oct 2026, 15:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: zotregistry.dev/zot/v2 2.1.15. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go zotregistry.dev/zot/v2: affected < 2.1.15; fixed in 2.1.15
- Go zotregistry.dev/zot: affected >= 1.3.0-20210831063041-c8779d9e87d9, <= 1.4.4-20251014054906-73eef25681af

## Suggested inspection (read-only)
- Go zotregistry.dev/zot/v2: check the installed version with your package manager.
- Go zotregistry.dev/zot: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on zotregistry.dev/zot/v2, zotregistry.dev/zot.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-85jx-fm8m-x8c6 (GitHub-reviewed advisory GHSA-85jx-fm8m-x8c6 lists affected ranges: Go zotregistry.dev/zot/v2 >=0 =1.3.0-20210831063041-c8779d9e87d9 <=1.4.4-20251014054906-73eef25681af)

Commands are suggestions: review each one before running it.

Loading voting…