Debian Package Tracker
Register | Log in
Subscribe

cosign

Code signing/transparency for containers and binaries (program)

Choose email to subscribe with

general
  • source: cosign (main)
  • version: 2.5.0-2
  • maintainer: Debian Go Packaging Team (DMD)
  • uploaders: Simon Josefsson [DMD]
  • arch: all any
  • std-ver: 4.7.2
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • stable: 2.5.0-2
  • testing: 2.5.0-2
  • unstable: 2.5.0-2
versioned links
  • 2.5.0-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • cosign (1 bugs: 0, 1, 0, 0)
  • golang-github-sigstore-cosign-dev
action needed
A new upstream version is available: 3.0.4 high
A new upstream version 3.0.4 is available, you should consider packaging it.
Created: 2025-11-27 Last update: 2026-01-13 18:18
1 security issue in trixie high

There is 1 open security issue in trixie.

1 important issue:
  • CVE-2026-22703: Cosign provides code signing and transparency for containers and binaries. Prior to versions 2.6.2 and 3.0.4, Cosign bundle can be crafted to successfully verify an artifact even if the embedded Rekor entry does not reference the artifact's digest, signature or public key. When verifying a Rekor entry, Cosign verifies the Rekor entry signature, and also compares the artifact's digest, the user's public key from either a Fulcio certificate or provided by the user, and the artifact signature to the Rekor entry contents. Without these comparisons, Cosign would accept any response from Rekor as valid. A malicious actor that has compromised a user's identity or signing key could construct a valid Cosign bundle by including any arbitrary Rekor entry, thus preventing the user from being able to audit the signing event. This issue has been patched in versions 2.6.2 and 3.0.4.
Created: 2026-01-10 Last update: 2026-01-11 06:30
1 security issue in sid high

There is 1 open security issue in sid.

1 important issue:
  • CVE-2026-22703: Cosign provides code signing and transparency for containers and binaries. Prior to versions 2.6.2 and 3.0.4, Cosign bundle can be crafted to successfully verify an artifact even if the embedded Rekor entry does not reference the artifact's digest, signature or public key. When verifying a Rekor entry, Cosign verifies the Rekor entry signature, and also compares the artifact's digest, the user's public key from either a Fulcio certificate or provided by the user, and the artifact signature to the Rekor entry contents. Without these comparisons, Cosign would accept any response from Rekor as valid. A malicious actor that has compromised a user's identity or signing key could construct a valid Cosign bundle by including any arbitrary Rekor entry, thus preventing the user from being able to audit the signing event. This issue has been patched in versions 2.6.2 and 3.0.4.
Created: 2026-01-10 Last update: 2026-01-11 06:30
1 security issue in forky high

There is 1 open security issue in forky.

1 important issue:
  • CVE-2026-22703: Cosign provides code signing and transparency for containers and binaries. Prior to versions 2.6.2 and 3.0.4, Cosign bundle can be crafted to successfully verify an artifact even if the embedded Rekor entry does not reference the artifact's digest, signature or public key. When verifying a Rekor entry, Cosign verifies the Rekor entry signature, and also compares the artifact's digest, the user's public key from either a Fulcio certificate or provided by the user, and the artifact signature to the Rekor entry contents. Without these comparisons, Cosign would accept any response from Rekor as valid. A malicious actor that has compromised a user's identity or signing key could construct a valid Cosign bundle by including any arbitrary Rekor entry, thus preventing the user from being able to audit the signing event. This issue has been patched in versions 2.6.2 and 3.0.4.
Created: 2026-01-10 Last update: 2026-01-11 06:30
lintian reports 1 warning normal
Lintian reports 1 warning about this package. You should make the package lintian clean getting rid of them.
Created: 2025-08-27 Last update: 2025-08-27 09:30
Standards version of the package is outdated. wishlist
The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.3 instead of 4.7.2).
Created: 2025-12-23 Last update: 2025-12-23 20:00
news
[rss feed]
  • [2025-04-14] cosign 2.5.0-2 MIGRATED to testing (Debian testing watch)
  • [2025-04-12] Accepted cosign 2.5.0-2 (source) into unstable (Simon Josefsson)
  • [2025-04-12] cosign 2.4.3-2 MIGRATED to testing (Debian testing watch)
  • [2025-04-10] Accepted cosign 2.5.0-1 (source) into experimental (Simon Josefsson)
  • [2025-04-09] Accepted cosign 2.4.3-2 (source) into unstable (Simon Josefsson)
  • [2025-03-27] cosign 2.4.3-1 MIGRATED to testing (Debian testing watch)
  • [2025-03-17] Accepted cosign 2.4.3-1 (source) into unstable (Simon Josefsson)
  • [2025-01-22] cosign 2.4.1-2 MIGRATED to testing (Debian testing watch)
  • [2025-01-20] Accepted cosign 2.4.1-2 (source) into unstable (Simon Josefsson)
  • [2025-01-19] Accepted cosign 2.4.1-1 (source amd64 all) into experimental (Simon Josefsson)
bugs [bug history graph]
  • all: 1
  • RC: 0
  • I&N: 1
  • M&W: 0
  • F&P: 0
  • patch: 0
links
  • homepage
  • lintian (0, 1)
  • buildd: logs, reproducibility, cross
  • popcon
  • browse source code
  • edit tags
  • other distros
  • security tracker
  • screenshots
  • debian patches
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 2.5.0-2

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing