# CVE-2026-41888: Distribution: Tag deletion bypasses `storage.delete.enabled` configuration > Attackers can delete container image tags even when deletion is disabled in configuration, compromising registry integrity. - **Severity:** Medium 6.3 (`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`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 14 May 2026 - **Updated:** 14 May 2026 - **Also known as:** BIT-distribution-2026-41888, CLEANSTART-2026-CX76698, DEBIAN-CVE-2026-41888, GHSA-6pjf-3r9x-m592, GO-2026-5185, MINI-3q8x-6cjp-2p73, MINI-3qj6-mw3g-wv5w, MINI-3rxw-cf66-xfmg, MINI-4fv8-49v7-whvq, MINI-5w4g-8cxc-p3rv, MINI-6pfv-h4xm-m64g, MINI-6r8h-9f6m-2rjw, MINI-6w3f-3g63-fgm2, MINI-726w-cprx-pmv6, MINI-8496-2hfj-x38w, MINI-8w55-f4wm-6222, MINI-ccc5-f355-4hv2, MINI-cxrc-r6m7-xp9p, MINI-gj8q-66j6-rh8c, MINI-jh3j-62m4-6p8v, MINI-m8gm-wvjg-xwv7, MINI-q4r5-4vjq-fx6h, MINI-qgxp-p5gg-4w32, MINI-r4mq-28hv-m93j, MINI-r7gm-m738-7pw6, MINI-vqc9-mc2c-cwwx, MINI-x3mq-v9wh-gg84, UBUNTU-CVE-2026-41888, openSUSE-SU-2026:10812-1, openSUSE-SU-2026:10814-1 ## What is CVE-2026-41888? CVE-2026-41888 is a medium-severity vulnerability in distribution, published on 14 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.1, tag deletion via the DELETE /v2//manifests/ 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. This vulnerability is fixed in 3.1.1. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2026-41888? 7 open source packages ship an affected version, including github.com/distribution/distribution, distribution and github.com/distribution/distribution/v3. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/distribution/distribution` | Go | All versions | None | | `github.com/distribution/distribution` | Go | All versions to 2.8.3 | None | | `github.com/distribution/distribution` | Go | All versions to 2.8.3 | None | | `distribution` | Bitnami | All versions | 3.1.1 | | `github.com/distribution/distribution/v3` | Go | All versions | 3.1.1 | | `github.com/distribution/distribution/v3` | Go | All versions | 3.1.1 | | `github.com/distribution/distribution/v3` | Go | All versions | 3.1.1 | | `distribution` | openSUSE:Tumbleweed | All versions | 3.1.1-1.1 | | `helm` | openSUSE:Tumbleweed | All versions | 4.2.0-1.1 | Products: Distribution Distribution. ## How do I fix CVE-2026-41888? Upgrade to a fixed version. ## Is CVE-2026-41888 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41888 exists. ## Other vulnerabilities in distribution - [CVE-2026-35172](https://insights.sbomify.com/CVE-2026-35172/): Distribution has stale blob access resurrection via repo-scoped redis descriptor cache invalidation (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-41888 and fix it if it is affected. What it is: CVE-2026-41888 is a medium-severity vulnerability in distribution, published on 14 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41888 exists. Affected packages and fixed versions: - github.com/distribution/distribution (Go): affected all versions; no fix listed - github.com/distribution/distribution (Go): affected all versions up to 2.8.3; no fix listed - github.com/distribution/distribution (Go): affected all versions up to 2.8.3; no fix listed - distribution (Bitnami): affected all versions; fixed in 3.1.1 - github.com/distribution/distribution/v3 (Go): affected all versions; fixed in 3.1.1 - github.com/distribution/distribution/v3 (Go): affected all versions; fixed in 3.1.1 - github.com/distribution/distribution/v3 (Go): affected all versions; fixed in 3.1.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-41888/ (Markdown: https://insights.sbomify.com/CVE-2026-41888/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41888 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41888 - OSV: https://osv.dev/vulnerability/CVE-2026-41888 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-41888/ Summaries are generated and may contain mistakes; the official description above is the record.