New MCP server — Bring vulnerability intelligence into your AI
Back to feed

CVE-2026-31801

ExploitedNVDCIRCLENISA

EUVD-2026-10890 · Published Mar 10, 2026

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

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 create but not update on a repository.
  2. ensure the repository has an existing tag named latest.
  3. attempt to push a new manifest to /v2/acme/app/manifests/latest (example repository name).
  4. observe that the authorization check is evaluated as create (not update) for latest, so the request passes authorization even though the tag already exists.

the attached poc demonstrates this deterministically with canonical.log and control.log markers.

expected vs actual

  • expected: overwriting an existing tag should require update permission, including latest (or latest should be explicitly documented as exempt).
  • actual: when reference=="latest" and the tag exists, the middleware keeps the action as create instead of switching to update.

security impact

this can break least-privilege expectations in deployments that rely on the create vs update split to prevent tag overwrites (for example, “push-once” policies). if latest is used as a high-trust tag in ci/cd, this can create supply-chain risk because a create-only principal can overwrite an existing latest tag while other existing tags correctly require update.

suggested fix

remove the special-case exemption for latest when determining whether an existing tag requires update permission (treat latest the same as other tags), or document and enforce an explicit policy rule for latest.

notes / rationale

  • oci distribution spec does not define a standard authorization model; this report is about zot’s own create vs update semantics and the observable behavior in DistSpecAuthzHandler.
  • zot documentation describes immutable tags as being enforceable via authorization policies (create-only “push once”, update disallowed). if latest is exempt, this control does not apply to latest unless documented otherwise.

addendum.md
poc.zip
PR_DESCRIPTION.md
RUNNABLE_POC.md

Technologies

Zotregistry ZotZotregistry.Dev Zot V2Zotregistry.Dev Zot

Weaknesses

CWE-863

CVSS scores

  • v3.17.7CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N

MITRE ATT&CK

Inferred

Where this vulnerability fits in an attack

Initial Access

References

Potentially impacted assets

See if this affects your attack surface

Latest trending attack

Critical6d ago

Multiple Vulnerabilities in SAP - Unauthenticated Authentication Bypass & Authentication Bypass via Default ACL & Unauthenticated Remote Memory Corruption & Remote Code Execution

SAP NetWeaver Application Server ABAP is the application server and runtime of SAP's ABAP platform. It runs SAP business applications such as S/4HANA and ERP, and it handles authentication, authorization and RFC communication. CVE-2026-120017 No advisory, NVD entry or other public record for this identifier could be found, so the details below come only from the vulnerability-feed headline. The headline describes an unauthenticated authentication bypass in SAP NetWeaver AS ABAP. This suggests a remote attacker could access protected functionality without valid credentials. The affected versions, the exact flaw mechanism, the impact and the patch status are not confirmed by any source. The SAP Security Patch Day notes should be checked for the official details. CVE-2026-89103 The only source for this entry is the vulnerability feed headline: SAP Gateway default access control list (ACL) authentication bypass, classed as unauthenticated remote code execution. No NVD record, SAP Security Note or vendor advisory could be found for this identifier, so I could not confirm the root cause, the affected versions or the fix. The headline suggests that default ACL settings let an unauthenticated remote attacker bypass Gateway access controls, with impact comparable to remote code execution. This is unverified. The search turned up only unrelated SAP identifiers, such as the NetWeaver Message Server flaw CVE-2026-58240, and none of them can be tied to this entry. Check the SAP Support Portal security notes and the NVD entry directly. CVE-2026-89126 Only the vulnerability-feed headline describes this flaw. It is a memory corruption vulnerability in SAP Web Dispatcher that an unauthenticated remote attacker could exploit to achieve remote code execution. No advisory, NVD record or SAP Security Note for this identifier appeared in the searches I ran. Affected versions, patch status and the root cause are therefore unconfirmed. Related SAP Web Dispatcher and ICM memory corruption flaws exist under other identifiers, for example CVE-2025-42877 and CVE-2026-44756. I did not confirm that CVE-2026-89126 is linked to either of them. Check the SAP Support Portal Security Notes and the NVD for the authoritative details.

Take 15 minutes to discover our platform with our experts

Patrowl Intel platform screenshot