<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 15:29:49 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-07972</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-07972</link>
      <description>bdu:2026-07972</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-07972</guid>
    </item>
    <item>
      <title>BIT-distribution-2026-41888 — Distribution: Tag deletion bypasses `storage.delete.enabled` configuration</title>
      <link>https://cve.radiocsirt.org/vuln/bit-distribution-2026-41888</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: distribution&lt;/p&gt;
&lt;p&gt;Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.1, tag deletion via the DELETE /v2/&amp;lt;name&amp;gt;/manifests/&amp;lt;tag&amp;gt; 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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: distribution&lt;/p&gt;
&lt;p&gt;Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.1, tag deletion via the DELETE /v2/&amp;lt;name&amp;gt;/manifests/&amp;lt;tag&amp;gt; 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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-distribution-2026-41888</guid>
    </item>
    <item>
      <title>EUVD-2026-318611</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-318611</link>
      <description>EUVD-2026-318611</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-318611</guid>
    </item>
    <item>
      <title>fkie_cve-2026-41888</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-41888</link>
      <description>&lt;p&gt;Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.1, tag deletion via the DELETE /v2/&amp;lt;name&amp;gt;/manifests/&amp;lt;tag&amp;gt; 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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.1, tag deletion via the DELETE /v2/&amp;lt;name&amp;gt;/manifests/&amp;lt;tag&amp;gt; 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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-41888</guid>
    </item>
    <item>
      <title>GHSA-6pjf-3r9x-m592 — Distribution's tag deletion bypasses `storage.delete.enabled` configuration</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6pjf-3r9x-m592</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/distribution/distribution/v3, Go: github.com/distribution/distribution&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Tag deletion via the `DELETE /v2/&amp;lt;name&amp;gt;/manifests/&amp;lt;tag&amp;gt;` 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.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;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).&lt;/p&gt;
&lt;p&gt;However, tag deletion takes a separate code path that never checks this setting:&lt;/p&gt;
&lt;p&gt;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`.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;Using a paired down Distribution configuration that explicitly disables deletes, such as this one, stored as `config.yaml`:&lt;/p&gt;
&lt;p&gt;```yaml
version: 0.1
storage:
  delete:
    enabled: false
  filesystem:
    rootdirectory: /var/lib/registry
http:
  addr: :5000
```&lt;/p&gt;
&lt;p&gt;Start a local Distribution, mounting in the above configuration from the current directory:&lt;/p&gt;
&lt;p&gt;```shell
docker…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/distribution/distribution/v3, Go: github.com/distribution/distribution&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Tag deletion via the `DELETE /v2/&amp;lt;name&amp;gt;/manifests/&amp;lt;tag&amp;gt;` 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.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;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).&lt;/p&gt;
&lt;p&gt;However, tag deletion takes a separate code path that never checks this setting:&lt;/p&gt;
&lt;p&gt;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`.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;Using a paired down Distribution configuration that explicitly disables deletes, such as this one, stored as `config.yaml`:&lt;/p&gt;
&lt;p&gt;```yaml
version: 0.1
storage:
  delete:
    enabled: false
  filesystem:
    rootdirectory: /var/lib/registry
http:
  addr: :5000
```&lt;/p&gt;
&lt;p&gt;Start a local Distribution, mounting in the above configuration from the current directory:&lt;/p&gt;
&lt;p&gt;```shell
docker…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6pjf-3r9x-m592</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:10812-1 — distribution-registry-3.1.1-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10812-1</link>
      <description>&lt;p&gt;distribution-registry-3.1.1-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;distribution-registry-3.1.1-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:10812-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:21881-1 — Security update for helm</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:21881-1</link>
      <description>&lt;p&gt;Security update for helm&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for helm&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:21881-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-41888</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-41888</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: docker-registry, Ubuntu:Pro:18.04:LTS: docker-registry, Ubuntu:20.04:LTS: docker-registry, Ubuntu:Pro:22.04:LTS: docker-registry, Ubuntu:24.04:LTS: docker-registry, Ubuntu:25.10: docker-registry, Ubuntu:Pro:26.04:LTS: docker-registry&lt;/p&gt;
&lt;p&gt;Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.1, tag deletion via the DELETE /v2/&amp;lt;name&amp;gt;/manifests/&amp;lt;tag&amp;gt; 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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: docker-registry, Ubuntu:Pro:18.04:LTS: docker-registry, Ubuntu:20.04:LTS: docker-registry, Ubuntu:Pro:22.04:LTS: docker-registry, Ubuntu:24.04:LTS: docker-registry, Ubuntu:25.10: docker-registry, Ubuntu:Pro:26.04:LTS: docker-registry&lt;/p&gt;
&lt;p&gt;Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.1, tag deletion via the DELETE /v2/&amp;lt;name&amp;gt;/manifests/&amp;lt;tag&amp;gt; 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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-41888</guid>
    </item>
  </channel>
</rss>
