https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 18:43:38 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-07552 bdu:2026-07552 https://cve.radiocsirt.org/vuln/bdu:2026-07552 https://cve.radiocsirt.org/vuln/bit-distribution-2026-35172 <p><strong>Affected:</strong> Bitnami: distribution</p> <p>Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.0, distribution can restore read access in repo a after an explicit delete when storage.cache.blobdescriptor: redis and storage.delete.enabled: true are both enabled. The delete path clears the shared digest descriptor but leaves stale repo-scoped membership behind, so a later Stat or Get from repo b repopulates the shared descriptor and makes the deleted blob readable from repo a again. This vulnerability is fixed in 3.1.0.</p> <p><strong>Affected:</strong> Bitnami: distribution</p> <p>Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.0, distribution can restore read access in repo a after an explicit delete when storage.cache.blobdescriptor: redis and storage.delete.enabled: true are both enabled. The delete path clears the shared digest descriptor but leaves stale repo-scoped membership behind, so a later Stat or Get from repo b repopulates the shared descriptor and makes the deleted blob readable from repo a again. This vulnerability is fixed in 3.1.0.</p> https://cve.radiocsirt.org/vuln/bit-distribution-2026-35172 https://cve.radiocsirt.org/vuln/cleanstart-2026-ac01087 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: gitness</p> <p>Multiple security vulnerabilities affect the gitness package. During chain building, the amount of work that is done is not correctly limited when a large number of intermediate certificates are passed in VerifyOptions. See references for individual vulnerability details.</p> <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: gitness</p> <p>Multiple security vulnerabilities affect the gitness package. During chain building, the amount of work that is done is not correctly limited when a large number of intermediate certificates are passed in VerifyOptions. See references for individual vulnerability details.</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-ac01087 https://cve.radiocsirt.org/vuln/euvd-2026-365487 EUVD-2026-365487 https://cve.radiocsirt.org/vuln/euvd-2026-365487 https://cve.radiocsirt.org/vuln/fkie_cve-2026-35172 <p>Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.0, distribution can restore read access in repo a after an explicit delete when storage.cache.blobdescriptor: redis and storage.delete.enabled: true are both enabled. The delete path clears the shared digest descriptor but leaves stale repo-scoped membership behind, so a later Stat or Get from repo b repopulates the shared descriptor and makes the deleted blob readable from repo a again. This vulnerability is fixed in 3.1.0.</p> <p>Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.0, distribution can restore read access in repo a after an explicit delete when storage.cache.blobdescriptor: redis and storage.delete.enabled: true are both enabled. The delete path clears the shared digest descriptor but leaves stale repo-scoped membership behind, so a later Stat or Get from repo b repopulates the shared descriptor and makes the deleted blob readable from repo a again. This vulnerability is fixed in 3.1.0.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-35172 https://cve.radiocsirt.org/vuln/ghsa-f2g3-hh2r-cwgc <p><strong>Affected:</strong> Go: github.com/distribution/distribution/v3, Go: github.com/distribution/distribution</p> <p>## summary: distribution can restore read access in `repo a` after an explicit delete when `storage.cache.blobdescriptor: redis` and `storage.delete.enabled: true` are both enabled. the delete path clears the shared digest descriptor but leaves stale repo-scoped membership behind, so a later `Stat` or `Get` from `repo b` repopulates the shared descriptor and makes the deleted blob readable from `repo a` again.</p> <p>## Severity</p> <p>HIGH</p> <p>justification: this is a repo-local authorization bypass after explicit delete, with concrete confidentiality impact and no requirement for write access after the delete event. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (7.5). CWE-284.</p> <p># affected version</p> <p>- repository: https://github.com/distribution/distribution - commit: ab67ffa0bda3712991194841d0fde727464feeb9 - affected versions: \&lt;= 3.0.x, \&lt;= 2.8.x when redis blob descriptor cache and delete are both enabled - affected file: - https://github.com/distribution/distribution/blob/ab67ffa0bda3712991194841d0fde727464feeb9/registry/storage/cache/redis/redis.go#L212-L226 - related callsites: - https://github.com/distribution/distribution/blob/ab67ffa0bda3712991194841d0fde727464feeb9/registry/storage/cache/cachedblobdescriptorstore.go#L66-L76 - https://github.com/distribution/distribution/blob/ab67ffa0bda3712991194841d0fde727464feeb9/registry/storage/linkedblobstore.go#L218-L224 - https://github.com/distribution/distribution/blob/ab67ffa0bda3712991194841d0fde727464feeb9/registry/storage/link…</p> <p><strong>Affected:</strong> Go: github.com/distribution/distribution/v3, Go: github.com/distribution/distribution</p> <p>## summary: distribution can restore read access in `repo a` after an explicit delete when `storage.cache.blobdescriptor: redis` and `storage.delete.enabled: true` are both enabled. the delete path clears the shared digest descriptor but leaves stale repo-scoped membership behind, so a later `Stat` or `Get` from `repo b` repopulates the shared descriptor and makes the deleted blob readable from `repo a` again.</p> <p>## Severity</p> <p>HIGH</p> <p>justification: this is a repo-local authorization bypass after explicit delete, with concrete confidentiality impact and no requirement for write access after the delete event. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (7.5). CWE-284.</p> <p># affected version</p> <p>- repository: https://github.com/distribution/distribution - commit: ab67ffa0bda3712991194841d0fde727464feeb9 - affected versions: \&lt;= 3.0.x, \&lt;= 2.8.x when redis blob descriptor cache and delete are both enabled - affected file: - https://github.com/distribution/distribution/blob/ab67ffa0bda3712991194841d0fde727464feeb9/registry/storage/cache/redis/redis.go#L212-L226 - related callsites: - https://github.com/distribution/distribution/blob/ab67ffa0bda3712991194841d0fde727464feeb9/registry/storage/cache/cachedblobdescriptorstore.go#L66-L76 - https://github.com/distribution/distribution/blob/ab67ffa0bda3712991194841d0fde727464feeb9/registry/storage/linkedblobstore.go#L218-L224 - https://github.com/distribution/distribution/blob/ab67ffa0bda3712991194841d0fde727464feeb9/registry/storage/link…</p> https://cve.radiocsirt.org/vuln/ghsa-f2g3-hh2r-cwgc https://cve.radiocsirt.org/vuln/opensuse-su-2026:10631-1 <p>distribution-registry-3.1.0-1.1 on GA media</p> <p>distribution-registry-3.1.0-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:10631-1 https://cve.radiocsirt.org/vuln/rhsa-2026:23234 <p>google.golang.org/grpc/grpc-go: google.golang.org/grpc/authz: gRPC-Go: Authorization bypass due to improper HTTP/2 path validation github.com/distribution/distribution: Distribution: Information disclosure via stale references after content deletion</p> <p>google.golang.org/grpc/grpc-go: google.golang.org/grpc/authz: gRPC-Go: Authorization bypass due to improper HTTP/2 path validation github.com/distribution/distribution: Distribution: Information disclosure via stale references after content deletion</p> https://cve.radiocsirt.org/vuln/rhsa-2026:23234 https://cve.radiocsirt.org/vuln/suse-su-2026:21560-1 <p>Security update for distribution</p> <p>Security update for distribution</p> https://cve.radiocsirt.org/vuln/suse-su-2026:21560-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-35172 <p><strong>Affected:</strong> 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</p> <p>Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.0, distribution can restore read access in repo a after an explicit delete when storage.cache.blobdescriptor: redis and storage.delete.enabled: true are both enabled. The delete path clears the shared digest descriptor but leaves stale repo-scoped membership behind, so a later Stat or Get from repo b repopulates the shared descriptor and makes the deleted blob readable from repo a again. This vulnerability is fixed in 3.1.0.</p> <p><strong>Affected:</strong> 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</p> <p>Distribution is a toolkit to pack, ship, store, and deliver container content. Prior to 3.1.0, distribution can restore read access in repo a after an explicit delete when storage.cache.blobdescriptor: redis and storage.delete.enabled: true are both enabled. The delete path clears the shared digest descriptor but leaves stale repo-scoped membership behind, so a later Stat or Get from repo b repopulates the shared descriptor and makes the deleted blob readable from repo a again. This vulnerability is fixed in 3.1.0.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-35172 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2072 <p>Ein Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um beliebigen Programmcode auszuführen, und um Informationen offenzulegen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um beliebigen Programmcode auszuführen, und um Informationen offenzulegen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2072