Categories
CVE-2026-61833 high CVSS 8.1

Vulnerability in zotregistry.dev/zot/v2 (CVE-2026-61833)

Summary

Vulnerability in zotregistry.dev/zot/v2 (CVE-2026-61833). Data can be tampered with by attackers. Exploitable via pull. Mitigation: upgrade to 2.1.18 or later.

Original description

The description as published by the source.

Summary

A bearer token with only pull and push scopes can successfully delete manifests and blobs from a zot registry. The bearer authentication handler maps all non-GET/HEAD HTTP methods, including DELETE, to the "push" action, and the DistSpecAuthzHandler middleware is bypassed entirely for bearer-authenticated requests. This allows any client holding a push-only bearer token to delete arbitrary manifests and blobs within the token's repository scope, in violation of the Docker Distribution Token Authentication Specification.

Details

The vulnerability exists in two interacting components:

1. Action Mapping Collapse (pkg/api/authn.go:571–586)

The bearer authentication handler maps HTTP methods to token scope actions using a binary check:

action := "pull"
if m := request.Method; m != http.MethodGet && m != http.MethodHead {
    action = "push"
}

This collapses DELETE, PUT, PATCH, and POST into a single "push" action. The "delete" action is never assigned.

2. Authorization Bypass for Bearer Auth (pkg/api/authz.go:270–275, 318–323)

When a request is authenticated via bearer token, the DistSpecAuthzHandler middleware, which performs fine-grained action inference (distinguishing create, read, update, and delete) is bypassed entirely:

if err != nil || (authnMwCtx != nil && authnMwCtx.AuthnType == BEARER) {
    next.ServeHTTP(response, request)
    ret…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-61833 has been found in zotregistry.dev/zot/v2.
Attackers can target a specific entry point like pull over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.1/10.
What to do: upgrade zotregistry.dev/zot/v2 to 2.1.18 or later.
If unsure, ask your IT team or search "zotregistry.dev/zot/v2 CVE-2026-61833" on the vendor's site.

CVE-2026-61833 (zotregistry.dev/zot/v2) — CWE-285 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: pull / push / DistSpecAuthzHandler / create
Patched: 2.1.18 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-285) exists in zotregistry.dev/zot/v2. Attackers reach the vulnerable code path via pull.

📍 Affected scope

Check the vendor advisory for the affected versions of zotregistry.dev/zot/v2. Attack surface: pull / push / DistSpecAuthzHandler / create.

🔥 Severity

Severity: High (CVSS 8.1/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 2.1.18.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'zotregistry.dev/zot/v2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'zotregistry.dev/zot/v2' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で zotregistry.dev/zot/v2 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade zotregistry.dev/zot/v2 to 2.1.18

    ステージング環境で 2.1.18 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go zotregistry.dev/zot/v2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.18"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details