CVE-2026-41888: Github.com/distribution/distribution/v3 Distribution's Tag Deletion Bypasses `storage.delete.enabled` Vulnerability

MODERATE
Advisory Identifier: GHSA-6pjf-3r9x-m592
CWE-863
Published
Advisory Summary

CVE-2026-41888 is a MODERATE distribution's tag deletion bypasses `storage.delete.enabled` vulnerability (CWE-863: Incorrect Authorization) affecting Github.com/distribution/distribution/v3 libraries in the Go ecosystem. The issue involves distribution's tag deletion bypasses `storage.delete.enabled` configuration. Remediation is available by upgrading affected packages to version 3.1.1.

CVE-2026-41888 at a Glance

CVE Identifier CVE-2026-41888
GHSA Identifier GHSA-6pjf-3r9x-m592
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-863: Incorrect Authorization
Affected Product Github.com/distribution/distribution/v3
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-41888

To remediate this vulnerability, upgrade all affected Github.com/distribution/distribution/v3 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/distribution/distribution/v3 fixed: 3.1.1
Upgrade github.com/distribution/distribution/v3 to 3.1.1
github.com/distribution/distribution fixed: Latest secure release
Upgrade github.com/distribution/distribution to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/distribution/distribution/v3

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-41888, inspect your project dependencies for Github.com/distribution/distribution/v3:

inspect dependencies for github.com/distribution/distribution/v3

Analyze the terminal output to locate any version of Github.com/distribution/distribution/v3 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.1.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. In Github.com/distribution/distribution/v3, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary Tag deletion via the `DELETE /v2/<name>/manifests/<tag>` endpoint bypasses the `storage.delete.enabled: false` configuration, allowing any API client to remove tags from repositories even when the operator has explicitly disabled deletion. ### Details When `storage.delete.enabled` is configured to false, digest-based manifest deletion is correctly rejected by the guard in [registry/storage/linkedblobstore.go:212-215](https://github.com/distribution/distribution/blob/main/registry/storage/linkedblobstore.go#L213-L215). However, tag deletion takes a separate code path that never checks this setting: In [`registry/handlers/manifests.go:439-453`](https://github.com/distribution/distribution/blob/main/registry/handlers/manifests.go#L439-L453), `DeleteManifest` detects a tag reference, calls `tagService.Untag()`, returns, never consulting `registry.deleteEnabled`. In turn, [`tagStore.Untag()`](https://github.com/distribution/distribution/blob/main/registry/storage/tagstore.go#L111-L121) calls the storage driver directly to delete the tag path without checking whether deletes are enabled. ### PoC Using a paired down Distribution configuration that explicitly disables deletes, such as this one, stored as `config.yaml`: ```yaml version: 0.1 storage: delete: enabled: false filesystem: rootdirectory: /var/lib/registry http: addr: :5000 ``` Start a local Distribution, mounting in the above configuration from the current directory: ```shell docker run -p 5000:5000 -v "$(pwd)/config.yaml":/config.yaml --restart=always --name registry registry:3.1.0 /config.yaml ``` In a separate terminal session/tab, push `alpine:3.23` into the running instance: ```shell docker pull alpine:3.23 docker tag alpine:3.23 localhost:5000/alpine:3.23 docker push localhost:5000/alpine:3.23 ``` Confirm that the tag shows up as expected: ```shell curl 'http://localhost:5000/v2/alpine/tags/list' {"name":"alpine","tags":["3.23"]} ``` Issue a delete for the `3.23` tag: ```shell curl -X DELETE 'http://localhost:5000/v2/alpine/manifests/3.23' ``` Observe that the tag is now gone, despite deletes being disabled: ```shell curl 'http://localhost:5000/v2/alpine/tags/list' {"name":"alpine","tags":null} ``` ### Impact This is an authorization bypass vulnerability. Any client with network access to the registry can delete tags despite the operator having disabled deletion. This can cause denial of service for consumers pulling by tag and enables supply-chain disruption by removing trusted tags from a registry that the operator and/or users believed to be immutable.

CVE-2026-41888 Affected Github.com/distribution/distribution/v3 Versions

2 component(s)
Fixed Versions:
3.1.1
Product / Package Ecosystem Affected Versions Fixed Version
github.com/distribution/distribution/v3
Go
< 3.1.1
3.1.1
github.com/distribution/distribution
Go
≤ 2.8.3

References

Frequently Asked Questions

What is CVE-2026-41888?
CVE-2026-41888 is a security vulnerability in Github.com/distribution/distribution/v3 involving Distribution's tag deletion bypasses `storage.delete.enabled` configuration under CWE-863: Incorrect Authorization.
Which Github.com/distribution/distribution/v3 versions are affected?
Affected versions include releases prior to 3.1.1 across affected packages: github.com/distribution/distribution/v3, github.com/distribution/distribution.
What version fixes CVE-2026-41888?
Upgrading to 3.1.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/distribution/distribution/v3 affected?
Yes, github.com/distribution/distribution/v3 is affected in releases prior to 3.1.1. Upgrade your dependency to 3.1.1 or later.
Is github.com/distribution/distribution affected?
Yes, github.com/distribution/distribution is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What CWE is associated with CVE-2026-41888?
CVE-2026-41888 is classified under CWE-863: Incorrect Authorization (The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.).
How can I check Go dependencies for CVE-2026-41888?
Run the dependency tree command: 'inspect dependencies for github.com/distribution/distribution/v3'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-6pjf-3r9x-m592",
  "modified" : "2026-07-21T13:45:53Z",
  "published" : "2026-05-04T20:48:57Z",
  "aliases" : [ "CVE-2026-41888" ],
  "summary" : "Distribution's tag deletion bypasses `storage.delete.enabled` configuration",
  "details" : "### Summary\n\nTag deletion via the `DELETE /v2/<name>/manifests/<tag>` endpoint bypasses the `storage.delete.enabled: false` configuration, allowing any API client to remove tags from repositories even when the operator has explicitly disabled deletion.\n\n### Details\n\nWhen `storage.delete.enabled` is configured to false, digest-based manifest deletion is correctly rejected by the guard in [registry/storage/linkedblobstore.go:212-215](https://github.com/distribution/distribution/blob/main/registry/storage/linkedblobstore.go#L213-L215). \n\nHowever, tag deletion takes a separate code path that never checks this setting:\n\nIn [`registry/handlers/manifests.go:439-453`](https://github.com/distribution/distribution/blob/main/registry/handlers/manifests.go#L439-L453), `DeleteManifest`  detects a tag reference, calls `tagService.Untag()`, returns,  never consulting `registry.deleteEnabled`.\n\nIn turn, [`tagStore.Untag()`](https://github.com/distribution/distribution/blob/main/registry/storage/tagstore.go#L111-L121) calls the storage driver directly to delete the tag path without checking whether deletes are enabled.\n\n### PoC\n\nUsing a paired down Distribution configuration that explicitly disables deletes, such as this one, stored as `config.yaml`:\n\n```yaml\nversion: 0.1\nstorage:\n  delete:\n    enabled: false\n  filesystem:\n    rootdirectory: /var/lib/registry\nhttp:\n  addr: :5000\n```\n\nStart a local Distribution, mounting in the above configuration from the current directory:\n\n```shell\ndocker run -p 5000:5000 -v \"$(pwd)/config.yaml\":/config.yaml --restart=always --name registry registry:3.1.0 /config.yaml\n```\n\nIn a separate terminal session/tab, push `alpine:3.23` into the running instance:\n```shell\ndocker pull alpine:3.23\ndocker tag alpine:3.23 localhost:5000/alpine:3.23\ndocker push localhost:5000/alpine:3.23\n```\n\nConfirm that the tag shows up as expected:\n```shell\ncurl 'http://localhost:5000/v2/alpine/tags/list'\n{\"name\":\"alpine\",\"tags\":[\"3.23\"]}\n```\n\nIssue a delete for the `3.23` tag:\n```shell\ncurl -X DELETE 'http://localhost:5000/v2/alpine/manifests/3.23'\n```\n\nObserve that the tag is now gone, despite deletes being disabled:\n```shell\ncurl 'http://localhost:5000/v2/alpine/tags/list'\n{\"name\":\"alpine\",\"tags\":null}\n```\n\n### Impact\n\nThis is an authorization bypass vulnerability. Any client with network access to the registry can delete tags despite the operator having disabled deletion. This can cause denial of service for consumers pulling by tag and enables supply-chain disruption by removing trusted tags from a registry that the operator and/or users believed to be immutable.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/distribution/distribution/v3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.1.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/distribution/distribution"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "2.8.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/distribution/distribution/security/advisories/GHSA-6pjf-3r9x-m592"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-41888"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/distribution/distribution"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-863" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-04T20:48:57Z",
    "nvd_published_at" : "2026-05-14T18:16:47Z"
  }
}