https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 16:55:17 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-01059 bdu:2026-01059 https://cve.radiocsirt.org/vuln/bdu:2026-01059 https://cve.radiocsirt.org/vuln/bell-cve-2026-23992 <p><strong>Affected:</strong> Alpaquita:stream: docker-cli-buildx</p> <p><strong>Affected:</strong> Alpaquita:stream: docker-cli-buildx</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-23992 https://cve.radiocsirt.org/vuln/cleanstart-2026-ba61304 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: cosign</p> <p>Package cosign version 2.4.3-r0 fixes 82 vulnerabilities: CVE-2025-0913, CVE-2025-15558, CVE-2025-22868, CVE-2025-22869, CVE-2025-22870...</p> <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: cosign</p> <p>Package cosign version 2.4.3-r0 fixes 82 vulnerabilities: CVE-2025-0913, CVE-2025-15558, CVE-2025-22868, CVE-2025-22869, CVE-2025-22870...</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-ba61304 https://cve.radiocsirt.org/vuln/euvd-2026-266313 EUVD-2026-266313 https://cve.radiocsirt.org/vuln/euvd-2026-266313 https://cve.radiocsirt.org/vuln/fkie_cve-2026-23992 <p>go-tuf is a Go implementation of The Update Framework (TUF). Starting in version 2.0.0 and prior to version 2.3.1, a compromised or misconfigured TUF repository can have the configured value of signature thresholds set to 0, which effectively disables signature verification. This can lead to unauthorized modification to TUF metadata files is possible at rest, or during transit as no integrity checks are made. Version 2.3.1 fixes the issue. As a workaround, always make sure that the TUF metadata roles are configured with a threshold of at least 1.</p> <p>go-tuf is a Go implementation of The Update Framework (TUF). Starting in version 2.0.0 and prior to version 2.3.1, a compromised or misconfigured TUF repository can have the configured value of signature thresholds set to 0, which effectively disables signature verification. This can lead to unauthorized modification to TUF metadata files is possible at rest, or during transit as no integrity checks are made. Version 2.3.1 fixes the issue. As a workaround, always make sure that the TUF metadata roles are configured with a threshold of at least 1.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-23992 https://cve.radiocsirt.org/vuln/ghsa-fphv-w9fq-2525 <p><strong>Affected:</strong> Go: github.com/theupdateframework/go-tuf/v2</p> <p># Security Disclosure: Improper validation of configured threshold for delegations</p> <p>## Summary</p> <p>A compromised or misconfigured TUF repository can have the configured value of signature thresholds set to 0, which effectively disables signature verification.</p> <p>## Impact</p> <p>Unathorized modification to TUF metadata files is possible at rest, or during transit as no integrity checks are made.</p> <p>## Patches</p> <p>Upgrade to v2.3.1</p> <p>## Workarounds</p> <p>Always make sure that the TUF metadata roles are configured with a threshold of at least 1.</p> <p>## Affected code:</p> <p>The `metadata.VerifyDelegate` did not verify the configured threshold prior to comparison. This means that a misconfigured TUF repository could disable the signature verification by setting the threshold to 0, or a negative value (and so always make the signature threshold computation to pass).</p> <p><strong>Affected:</strong> Go: github.com/theupdateframework/go-tuf/v2</p> <p># Security Disclosure: Improper validation of configured threshold for delegations</p> <p>## Summary</p> <p>A compromised or misconfigured TUF repository can have the configured value of signature thresholds set to 0, which effectively disables signature verification.</p> <p>## Impact</p> <p>Unathorized modification to TUF metadata files is possible at rest, or during transit as no integrity checks are made.</p> <p>## Patches</p> <p>Upgrade to v2.3.1</p> <p>## Workarounds</p> <p>Always make sure that the TUF metadata roles are configured with a threshold of at least 1.</p> <p>## Affected code:</p> <p>The `metadata.VerifyDelegate` did not verify the configured threshold prior to comparison. This means that a misconfigured TUF repository could disable the signature verification by setting the threshold to 0, or a negative value (and so always make the signature threshold computation to pass).</p> https://cve.radiocsirt.org/vuln/ghsa-fphv-w9fq-2525 https://cve.radiocsirt.org/vuln/opensuse-su-2026:10235-1 <p>cosign-3.0.5-1.1 on GA media</p> <p>cosign-3.0.5-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:10235-1 https://cve.radiocsirt.org/vuln/suse-su-2026:20904-1 <p>Security update for cosign</p> <p>Security update for cosign</p> https://cve.radiocsirt.org/vuln/suse-su-2026:20904-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23992 <p><strong>Affected:</strong> Ubuntu:24.04:LTS: golang-github-theupdateframework-go-tuf, Ubuntu:25.10: golang-github-theupdateframework-go-tuf, Ubuntu:26.04:LTS: golang-github-theupdateframework-go-tuf</p> <p>go-tuf is a Go implementation of The Update Framework (TUF). Starting in version 2.0.0 and prior to version 2.3.1, a compromised or misconfigured TUF repository can have the configured value of signature thresholds set to 0, which effectively disables signature verification. This can lead to unauthorized modification to TUF metadata files is possible at rest, or during transit as no integrity checks are made. Version 2.3.1 fixes the issue. As a workaround, always make sure that the TUF metadata roles are configured with a threshold of at least 1.</p> <p><strong>Affected:</strong> Ubuntu:24.04:LTS: golang-github-theupdateframework-go-tuf, Ubuntu:25.10: golang-github-theupdateframework-go-tuf, Ubuntu:26.04:LTS: golang-github-theupdateframework-go-tuf</p> <p>go-tuf is a Go implementation of The Update Framework (TUF). Starting in version 2.0.0 and prior to version 2.3.1, a compromised or misconfigured TUF repository can have the configured value of signature thresholds set to 0, which effectively disables signature verification. This can lead to unauthorized modification to TUF metadata files is possible at rest, or during transit as no integrity checks are made. Version 2.3.1 fixes the issue. As a workaround, always make sure that the TUF metadata roles are configured with a threshold of at least 1.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23992