cosign

No entries match these filters. Clear filters

1. v3.1.4 Oct 20, 2026 · issue 115

   cosign v3.1.4 adds cosign bundle create-from-container and shell completion for --slot.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   └──▷ GET THIS VERSION

   copy

   $ git clone --branch v3.1.4 https://github.com/sigstore/cosign.git
   # already have the repo? check out this version:
   $ git checkout v3.1.4

   └──▷ TRY IT
   Create a Sigstore bundle from an already-signed container image for offline or air-gapped verification workflows.
   copy

   $ cosign bundle create-from-container $IMAGE

   • Adds cosign bundle create-from-container subcommand to create a Sigstore bundle directly from a container image.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Adds shell completion for the --slot option argument.
   • Adds cosign bundle create-from-container subcommand to create a Sigstore bundle directly from a container image.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   1 more in Everything

2. v3.1.3 Aug 6, 2026 · issue 037

   cosign v3.1.3 adds X.509X.509A standard defining the format of public-key certificates, maintained by the ITU-T, used by cyber tools to authenticate identities and establish encrypted connections over TLS and similar protocols. certificate chain support for OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. signing and auto-detects digest algorithms for public keys.

   └──▷ GET THIS VERSION

   copy

   $ git clone --branch v3.1.3 https://github.com/sigstore/cosign.git
   # already have the repo? check out this version:
   $ git checkout v3.1.3

   • Auto-detects the default digest algorithm for public keys, removing the need to manually specify it.
   • Supports OCI signing with an X.509 certificate chain, enabling bring-your-own PKIPKIA framework of policies, roles, and cryptographic standards for issuing and managing digital certificates that bind public keys to identities, letting tools verify authenticity and encrypt communications without pre-shared secrets. workflows for container image signing.

   2 details in Everything

3. v3.1.2 Jul 17, 2026 · issue 019

   cosign v3.1.2 adds a bundle inspect command and a --base-config flag for signing-config overrides.

   └──▷ GET THIS VERSION

   copy

   $ git clone --branch v3.1.2 https://github.com/sigstore/cosign.git
   # already have the repo? check out this version:
   $ git checkout v3.1.2

   └──▷ TRY IT
   Inspect a local cosign bundle file to examine its contents and structure.
   copy

   $ cosign bundle inspect <bundle-file>

   Override specific services from a base signing config when configuring cosign for a custom environment.
   copy

   $ cosign signing-config --base-config <base-config-file>

   • Adds cosign bundle inspect command to examine cosign bundle files.
   • Adds --base-config flag to the signing-config command to override services from a base config.

   2 details in Everything

4. v3.1.1 Jun 9, 2026 · release notes

   cosign v3.1.1 adds a bundle upgrade command, Rekor v2 signing support, and makes the standardized bundle format the default.

   └──▷ GET THIS VERSION

   copy

   $ git clone --branch v3.1.1 https://github.com/sigstore/cosign.git
   # already have the repo? check out this version:
   $ git checkout v3.1.1

   └──▷ TRY IT
   Upgrade a legacy cosign bundle file to the standardized Sigstore bundle format before it becomes the only accepted format in v4.
   copy

   $ cosign bundle upgrade --bundle <path-to-existing.bundle>

   • Adds bundle upgrade subcommand to convert existing bundles to the standardized Sigstore bundle format.
   • Updates signing path to log to Rekor v2, with DSSE attestations logged as hashed entries using PAE encoding — unblocking large signed DSSEs like SBOMsSBOMsA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue..
   • Adds Rekor v2 flag to cosign signing-config create for configuring Rekor v2 in signing configs.
   • Makes the standardized Sigstore bundle format the default output for signing and default input for verification.
   • Signing now routes exclusively through sigstore-go.

   5 details in Everything

5. v3.1.1 Jun 9, 2026 · issue 001

   cosign v3.1.1 adds a bundle upgrade command, Rekor v2 support, and standardizes on the new bundle format by default.

   └──▷ GET THIS VERSION

   copy

   $ git clone --branch v3.1.1 https://github.com/sigstore/cosign.git
   # already have the repo? check out this version:
   $ git checkout v3.1.1

   └──▷ TRY IT
   Upgrade an existing legacy cosign bundle file to the new standardized Sigstore bundle format before v4 removes deprecated flag support.
   copy

   $ cosign bundle upgrade --bundle artifact.bundle

   Create a signing config that targets a Rekor v2 transparency log instance for environments running the updated Rekor stack.
   copy

   $ cosign signing-config create --rekor-v2 --out signing-config.json

   • Adds cosign bundle upgrade command to migrate existing bundles to the standardized Sigstore bundle format.
   • Adds Rekor v2 flag to cosign signing-config create, enabling configuration of Rekor v2 transparency log endpoints.
   • Signs exclusively via sigstore-go, unifying the signing path across Sigstore SDKs.
   • Updates DSSE attestation signing to log as hashed entries using PAE encoding in Rekor v2, unblocking upload of large signed DSSEs such as SBOMsSBOMsA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue..
   • Standardizes the new protobuf bundle format as the default output for signing and input for verification.

   +2 more show less

   • Deprecates certificate, signing-config, bundle, OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. referrer, and other v3.x flags slated for removal in Cosign v4.
   • Breaking change: cosign sign now requires either bundle output or registry upload — bare signing without a destination is no longer permitted.

   7 details in Everything

   └──▷ BREAKING ON UPGRADE

   • !Running cosign sign now requires either bundle output or registry upload (--bundle or registry push); omitting both is no longer accepted.
6. advisory CVE-2026-39395 Apr 6, 2026 · issue 128
   • CVE-2026-39395: verify-blob-attestation reports false positive when payload parsing fails (CVSSCVSSCommon Vulnerability Scoring System, a method for describing a vulnerability's characteristics and severity. Its score is not the probability that attackers will exploit it. 4.3, affects <= v3.0.5, <= v2.6.2)⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
7. v3.0.6 Apr 6, 2026 · release notes

   cosign v3.0.6 adds OpenBao-managed key signing, GitLab group key creation, and GCEGCEGoogle Compute Engine, Google's infrastructure-as-a-service platform for running virtual machines in the cloud; cyber tools use it for scalable, on-demand compute without managing physical hardware. metadata server support.

   └──▷ GET THIS VERSION

   copy

   $ git clone --branch v3.0.6 https://github.com/sigstore/cosign.git
   # already have the repo? check out this version:
   $ git checkout v3.0.6

   • Adds support for signing with OpenBao-managed keys.
   • Supports key creation scoped to a GitLab group.
   • Adds support for the GCE metadata server environment variable.
   • Disallows using --key and cert identity together during verification, enforcing cleaner verification flows.

   4 details in Everything

   └──▷ BREAKING ON UPGRADE

   • !Using --new-bundle-format and --rfc3161-timestamp together is now disallowed and will cause an error.
   • !Using --key and cert identity flags together during verification is now disallowed.
8. v2.6.3 Apr 6, 2026 · release notes

   Backports bundle detection to sign and attest subcommands in v2.6.3.

   └──▷ GET THIS VERSION

   copy

   $ git clone --branch v2.6.3 https://github.com/sigstore/cosign.git
   # already have the repo? check out this version:
   $ git checkout v2.6.3

   └──▷ TRY IT
   Sign a container image and upload the signature bundle automatically.
   copy

   $ cosign sign --bundle=true <image>

   Attest a payload and include the verification bundle in the output.
   copy

   $ cosign attest --bundle=true <payload>

   • Adds bundle flag to cosign sign command
   • Adds bundle flag to cosign attest command

   2 details in Everything

9. v3.0.5 Feb 19, 2026 · release notes

   cosign v3.0.5 adds mTLSmTLSMutual TLS, an encrypted connection where both client and server present certificates to prove their identity. It helps services verify who they are communicating with. for TSA signing, auto-requires signed timestamps with Rekor v2, and expands local image bundle support.

   └──▷ GET THIS VERSION

   copy

   $ git clone --branch v3.0.5 https://github.com/sigstore/cosign.git
   # already have the repo? check out this version:
   $ git checkout v3.0.5

   └──▷ TRY IT
   Sign a local OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. image tarball and produce a v2/v3 bundle format — now supported together with --local-image.
   copy

   $ cosign sign --local-image --new-bundle-format <path/to/image.tar>

   • Automatically requires a signed timestamp when working with Rekor v2 entries, strengthening timestamp integrity guarantees.
   • Adds mTLS support for TSA (Timestamp Authority) client connections when signing with a signing config.
   • Enforces TSA requirement for Rekor v2 and Fulcio signing workflows.
   • Supports --local-image combined with --new-bundle-format for v2 and v3 signatures.

   4 details in Everything

10. advisory CVE-2026-22703 Jan 9, 2026 · issue 128
    • CVE-2026-22703: Verification accepts any valid Rekor entry under certain conditions (CVSSCVSSCommon Vulnerability Scoring System, a method for describing a vulnerability's characteristics and severity. Its score is not the probability that attackers will exploit it. 5.5, affects <= 2.6.1, <= 3.0.3)⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
11. v3.0.4 Jan 9, 2026 · release notes

    cosign v3.0.4 adds default service support for trusted-root/signing-config creation and enables keyless offline verification

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v3.0.4 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v3.0.4

    • Supports default services when creating trusted-root and signing-config, reducing manual configuration.
    • Enables offline verification with a key without requiring a trusted root file.
    • Improves cosign tree performance via digest caching for faster artifact tree resolution.

    3 details in Everything

12. v3.0.3 Dec 10, 2025 · release notes

    cosign v3.0.3 extends protobuf bundle support to clean/save/load/download/tree and adds --signing-algorithm flag

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v3.0.3 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v3.0.3

    └──▷ TRY IT
    Bootstrap cosign against the Sigstore staging environment for pre-production testing.
    copy

    $ cosign initialize --staging

    • Adds protobuf bundle support to the clean, save, load, download, attach, and tree subcommands for broader new bundle format compatibility.
    • New --signing-algorithm flag lets callers specify the signing algorithm when signing artifacts.
    • Adds --bundle flag and corrects --upload behaviour for the new protobuf bundle format.
    • Enables sign-blob to sign with a certificate in addition to key-based signing.
    • Adds a staging flag to initialize for bootstrapping with staging TUF metadata.

    +3 more show less

    • Supports multiple container identities during verification.
    • Passes insecure registry flags through to referrers lookups.
    • Adds a warning when --output* flags are used with commands where their behaviour may be unexpected.

    8 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The --out flag is removed from cosign initialize; any scripts or workflows using it will break.
13. 3.0.2 Oct 10, 2025 · release notes

    Cosign v3.0.2 requires the --bundle flag for outputting Sigstore bundles and updates internal rekor-tiles pathing.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.0.2 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout 3.0.2

    • --bundle is now a required CLI flag (previously optional) to specify the output file for the Sigstore bundle containing verification material.

    1 detail in Everything

    └──▷ BREAKING ON UPGRADE

    • !The --bundle flag has moved from optional to required; commands that previously omitted it will fail to produce a bundle or error out.
14. v3.0.1 Oct 8, 2025 · release notes

    Cosign v3 enables protobuf bundle format, OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. 1.1 artifacts, and unified trust config by default.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v3.0.1 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v3.0.1

    • Enables standardized Sigstore protobuf bundle format by default (previously opt-in via --new-bundle-format).
    • Supports providing roots of trust and service URLs via a single --trusted-root or --signing-config file.
    • Fetches service URLs from the TUF PGI signing config by default, removing manual service URL configuration.
    • Makes --bundle flag required (not optional) when writing Sigstore bundle output files.

    4 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The --bundle flag (specifying an output file for the Sigstore bundle) is now required rather than optional.
15. v2.6.1 Oct 2, 2025 · release notes

    cosign verify now partially populates output when working with new Sigstore bundle formats

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v2.6.1 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v2.6.1

16. v2.6.0 Sep 12, 2025 · release notes

    cosign v2.6.0 adds in-toto statement signing, OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. 1.1 bundle artifacts, SigningConfig support, and alternative hash algorithms.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v2.6.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v2.6.0

    └──▷ TRY IT
    Sign and verify a container image, storing the bundle as an OCI 1.1 referring artifact for registries that support it.
    copy

    $ cosign sign --new-bundle-format=true ghcr.io/user/alpine@sha256:a19367999603840546b8612572e338ec076c6d1f2fec61760a9e11410f546733
    cosign verify --new-bundle-format=true ghcr.io/user/alpine@sha256:a19367999603840546b8612572e338ec076c6d1f2fec61760a9e11410f546733

    Sign and verify a blob using service URLs from the public-good TUF SigningConfig, required when targeting a Rekor v2 instance.
    copy

    $ cosign sign-blob --use-signing-config --bundle sigstore.json README.md
    cosign verify-blob --new-bundle-format --bundle sigstore.json --certificate-identity $EMAIL --certificate-oidc-issuer $ISSUER --use-signed-timestamps README.md

    • Supports signing a complete in-toto statement directly via attest-blob --statement instead of requiring cosign to construct one from a predicate.
    • Adds verify-blob-attestation support for verifying a statement's subject using --digest and --digestAlg instead of a file reference.
    • Uploads signatures and verification material as OCI Image 1.1 referring artifacts via --new-bundle-format=true on cosign sign and cosign verify.
    • Adds --use-signing-config flag to sign-blob, attest-blob, sign, and attest for providing service URLs via a SigningConfig, enabling use with Rekor v2 instances.
    • Supports self-managed keys when signing with the sigstore-go backend.

    +4 more show less

    • Removes SHA-256SHA-256A cryptographic hash function that turns data into a fixed 256-bit fingerprint. It is used to check integrity; hashing does not encrypt the original data. assumption in sign-blob/verify-blob, enabling alternative hash algorithms with keys.
    • Adds a terminal spinner during signing operations with the sigstore-go backend.
    • Skips TUF content loading when a trusted root path is explicitly specified.
    • No longer requires timestamps when verifying with a key (--use-signed-timestamps is optional in key-based verification).

    9 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !sign.SignerFromKeyOpts no longer generates a key; it now returns whether the client needs to generate a key, and callers must invoke sign.KeylessSigner themselves if so.
17. v2.5.3 Jul 17, 2025 · release notes

    cosign v2.5.3 adds a new signing-config create command, multi-service trusted-root, OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. 1.1+ tree support, and validity period controls.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v2.5.3 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v2.5.3

    └──▷ TRY IT
    Create a new signing config from the CLI to bootstrap a Sigstore deployment.
    copy

    $ cosign signing-config create

    Build a trusted root that covers multiple transparency/TSA services in one shot.
    copy

    $ cosign trusted-root create --tlog-url https://tlog1.example.com --tlog-url https://tlog2.example.com --out trusted_root.json

    • New signing-config create subcommand for generating signing configurations.
    • Allows multiple services to be specified when running trusted-root create.
    • Adds --validity-period-end (validity period end) option to trusted-root create for controlling certificate validity windows.
    • Adds experimental OCI 1.1+ support to the tree subcommand for inspecting OCI 1.1 referrer graphs.

    4 details in Everything

18. v2.5.1 Jun 16, 2025 · release notes

    cosign v2.5.1 adds Rekor v2 support and TUF v2 client to trusted-root create, plus relaxed private PKIPKIA framework of policies, roles, and cryptographic standards for issuing and managing digital certificates that bind public keys to identities, letting tools verify authenticity and encrypt communications without pre-shared secrets. validation.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v2.5.1 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v2.5.1

    • Adds Rekor v2 support to the trusted-root create command.
    • Adds --base-url and --uri flags to the trusted-root create command.
    • Upgrades to TUF v2 client with trusted root.
    • Skips SCT verification for private PKI certificates.
    • Relaxes EKU chain validation rules for TSA (Timestamp Authority) certificates.

    5 details in Everything

19. v2.5.0 Apr 7, 2025 · release notes

    cosign v2.5.0 adds new bundle format for OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. attestations and TSA certificate flags for cosign attest.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v2.5.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v2.5.0

    └──▷ TRY IT
    Attest an OCI image using the new bundle format to produce an OCI artifact-based attestation instead of the legacy format.
    copy

    $ cosign attest --new-bundle-format --predicate predicate.json --type slsaprovenance <image>

    • Supports the new bundle specification for attesting and verifying OCI image attestations uploaded as OCI artifacts, gated behind --new-bundle-format on cosign attest.
    • Adds TSA (Timestamp Authority) certificate-related flags and fields to cosign attest.
    • Adds non-filename shell completions for cosign commands.

    3 details in Everything

20. v2.4.3 Feb 19, 2025 · release notes

    cosign v2.4.3 adds KMSKMSA managed service that creates, stores, rotates and controls access to encryption keys, usually backed by HSMs. Applications ask it to encrypt or decrypt rather than holding keys themselves. plugin support, offline signature fetching, and improved file flag completion.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v2.4.3 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v2.4.3

    • Supports KMS plugins via updated sigstore/sigstore dependency, enabling third-party key management integrations.
    • Enables fetching signatures without a remote GET request, supporting restricted or offline verification workflows.
    • Improves file flag tab completion for a smoother CLI experience.

    3 details in Everything

21. v2.4.2 Feb 4, 2025 · release notes

    cosign v2.4.2 adds bundle/trusted-root create commands, mTLSmTLSMutual TLS, an encrypted connection where both client and server present certificates to prove their identity. It helps services verify who they are communicating with. registry support, and root checksum verification.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v2.4.2 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v2.4.2

    • New bundle create helper command for creating Sigstore bundles.
    • New trusted-root create helper command for creating trusted root configurations.
    • Supports mTLS towards container registries for mutual TLSmutual TLSMutual TLS, an encrypted connection where both client and server present certificates to prove their identity. It helps services verify who they are communicating with. authentication.
    • Adds root checksum verification in cosign initialize.
    • Adds UseSignedTimestamps to CheckOpts with refactored TSA options for timestamp authority verification.

    +2 more show less

    • Detects whether a user supplied a valid protobuf bundle and logs a message if --trusted-root is not provided.
    • Updates open-policy-agent library to 1.1.0 (Rego v0 policies supported).

    7 details in Everything

22. v2.4.0 Aug 6, 2024 · release notes

    cosign v2.4.0 adds Sigstore bundle format support for blob signing/verification and a new trust root file mechanism.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v2.4.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v2.4.0

    • Adds Sigstore specification-compliant bundle format support to verify-blob and verify-blob-attestation.
    • Adds protobuf bundle format support to sign-blob and attest-blob.
    • Adds support for recording creation timestamp in cosign attest.
    • Integrates a conformance test suite to verify signing and verification behavior.
    • Nightly cosign container builds now served from GHCRGHCRGitHub Container Registry, GitHub's hosted service for storing and distributing OCI-compatible container images, giving cyber tools a versioned, access-controlled image store tied directly to a GitHub repository. instead of GCR.

    +1 more show less

    • Includes SCT verification failure details in error messages.

    6 details in Everything

23. v2.3.0 Jul 22, 2024 · release notes

    cosign v2.3.0 adds registry options to save, a debug providers command, and new CA flag support for verify.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v2.3.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v2.3.0

    └──▷ TRY IT
    Verify a container image against an on-prem or private CA instead of the public Sigstore root.
    copy

    $ cosign verify --ca-roots ./corp-root-ca.pem --ca-intermediates ./corp-intermediate-ca.pem --certificate-identity user@example.com --certificate-oidc-issuer https://accounts.example.com registry.example.com/myapp:latest

    Inspect which OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user./signing providers cosign has detected in the current environment before signing.
    copy

    $ cosign debug providers

    • New cosign debug providers command to inspect configured OIDC/signing providers.
    • Adds --ca-roots and --ca-intermediates flags to cosign verify for custom CA chain verification.
    • Adds registry options (e.g. auth, TLS settings) to cosign save command.
    • Adds TSA certificate chain validation via environment variable or TUF targets for timestamp authority checks.
    • Extends keyless verification support across all cosign verify subcommands, not just verify.

    +1 more show less

    • New PayloadProvider interface decouples attestation payload handling from the oci.Signature interface.

    6 details in Everything

24. advisory CVE-2024-29903 Apr 10, 2024 · issue 128
    • CVE-2024-29903: Malicious artifacts can cause machine-wide DoS (CVSSCVSSCommon Vulnerability Scoring System, a method for describing a vulnerability's characteristics and severity. Its score is not the probability that attackers will exploit it. 4.2, affects <= 2.2.3)⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
25. v2.2.4 Apr 10, 2024 · release notes

    Supports Fulcio client credentials flow with an explicit argument

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v2.2.4 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v2.2.4

    └──▷ USE IT
    Authenticate against Fulcio using a service account or OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. provider via client credentials instead of interactive browser login.
    shell copy

    cosign sign --fulcio-client-credentials-flow --key <key_path> --set-oidc-issuer <issuer> --set-client-id <client_id> <image>

    • Adds --fulcio-client-credentials-flow flag to enable the Fulcio client credentials authentication flow

    1 detail in Everything

26. v2.2.3 Jan 31, 2024 · release notes

    cosign v2.2.3 adds OpenVEXOpenVEXAn open specification and Go library, maintained by the OpenVEX community, for expressing VEX (Vulnerability Exploitability eXchange) statements in a standard JSON format so cyber tools can automate vulnerability triage. predicate support and optional Rekor upload for attestations.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v2.2.3 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v2.2.3

    └──▷ USE IT
    Create an attestation using the new OpenVEX format.
    shell copy

    cosign attest --predicate <predicate_file> --type openvex <image>

    Upload an attestation to Rekor during creation.
    shell copy

    cosign attest --upload-rekor=true <flags> <image>

    • Add support for OpenVEX predicate type
    • Allow for option in cosign attest and attest-blob to upload attestation as supported in Rekor

    2 details in Everything

27. v2.2.2 Dec 5, 2023 · release notes

    cosign v2.2.2 adds --yes flag to import-key-pair and --private-infrastructure alias for private deployments

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v2.2.2 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v2.2.2

    • Adds --yes flag to cosign import-key-pair to skip overwrite confirmation
    • Uses the timeout flag value in verify* commands
    • Adds --private-infrastructure alias for --insecure-skip-log

    3 details in Everything

28. v2.2.1 Nov 7, 2023 · release notes

    cosign v2.2.1 adds SLSASLSASupply-chain Levels for Software Artifacts, a framework for assessing how software was built and protecting that process from tampering. Provenance records help verify where a build came from. 1.0 support, Rekor bundle attachment, registry auth options, and cosign copy flags

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v2.2.1 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v2.2.1

    └──▷ USE IT
    Copy only the signature and attestation layers from one image to another, skipping SBOMSBOMA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue.
    shell copy

    cosign copy --only sign,att <source_image> <dest_image>

    • Adds --only flag to cosign copy to selectively copy sign, attestation, and SBOM layers
    • Adds --platform flag to cosign copy for multi-arch image targeting
    • Enables Rekor bundle attachment to container images during signing
    • Exposes rekor response output on signing via new capability
    • Supports SLSA 1.0 attestation format

    +4 more show less

    • Adds support for basic auth and bearer auth login to registries
    • Allows ignoring certificates when using pkcs11
    • Provides image digest retrieval via the triangulate subcommand
    • Enables guard flag for experimental OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. 1.1 verify functionality

    9 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !DEPRECATED: SBOM attachments are deprecated and will be removed in a future release
29. v2.2.0 Aug 31, 2023 · release notes

    cosign v2.2.0 adds mTLSmTLSMutual TLS, an encrypted connection where both client and server present certificates to prove their identity. It helps services verify who they are communicating with. support to cosign sign and switches DSSE uploads to Rekor.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v2.2.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v2.2.0

    └──▷ USE IT
    Sign a container image using mutual TLSmutual TLSMutual TLS, an encrypted connection where both client and server present certificates to prove their identity. It helps services verify who they are communicating with. to authenticate with the keyless server.
    shell copy

    cosign sign --key cosign.pub \
      --cert /path/to/client.crt \
      --client-key /path/to/client.key \
      --ca /path/to/ca.crt \
      gcr.io/my-project/my-image:latest

    • Adds --client-cert, --client-key, and --ca flags to cosign sign for mTLS authentication
    • Switches default attestation upload type from intoto to DSSE for Rekor transparency log submission

    2 details in Everything

30. v2.1.0 Jun 24, 2023 · release notes

    Cosign v2.1.0 adds sign --sign-container-identity, TSA support in attach, parallel verify, and DSSE/rekor bundle types

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v2.1.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v2.1.0

    └──▷ USE IT
    Sign a container image while explicitly attaching its identity.
    shell copy

    cosign sign --sign-container-identity <image>

    Verify images using a specific certificate chain instead of default Fulcio roots.
    shell copy

    cosign verify --certificate-chain <path/to/cert> <image>

    Limit verification parallelism to avoid resource exhaustion on large images.
    shell copy

    cosign verify --max-workers 4 <image>

    • Adds --sign-container-identity flag to cosign sign for attaching container identity to signatures.
    • Adds TSA (Time Stamping Authority) response support in the attach command via a new mechanism.
    • Adds DSSE Rekor type bundle validation support, refactoring bundle validation code.
    • Enables parallel signature and attestation verification using worker pools controlled by --max-workers.
    • Allows overriding remote options for flexibility in network configuration.

    +6 more show less

    • Introduces 'no cert found on sig' exit code to handle missing certificate scenarios explicitly.
    • Supports --platform flag in download attestation commands for cross-platform filtering.
    • Enables keyless verification using only a provided certificate chain with non-Fulcio roots.
    • Accepts attachment-tag-prefix argument for cosign copy to control tag generation.
    • Adds --allow-insecure-registry flag to cosign load to permit connections to insecure registries.
    • Makes the predicate type a required --type flag in all attest commands.

    11 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The predicate is now a required flag in the attest commands, set via the --type flag.
31. v2.0.2 Apr 24, 2023 · release notes

    cosign v2.0.2 requires payload with signatures and removes sget command

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v2.0.2 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v2.0.2

    └──▷ TRY IT
    Verify that sget is removed by checking help output
    copy

    $ cosign --help | grep sget || echo 'sget command not found'

    • Removes the sget command from the CLI entirely.
    • Requires that a payload be provided alongside any signature operation.

    2 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The sget subcommand is no longer available and will return an error if invoked.
    • !Signature operations now fail unless a payload is explicitly provided via the relevant flags.
32. v2.0.1 Apr 6, 2023 · release notes

    cosign v2.0.1 adds Buildkite and env-var token providers, riscv64 support, and custom GOEXE

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v2.0.1 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v2.0.1

    • Add GOEXE environment variable to customise the Go executable used for building
    • Add RISC-V 64-bit (riscv64) architecture support for binaries
    • Add Buildkite OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. token provider integration
    • Add environment variable-based token provider
    • Add specific exit codes for verify errors

    5 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The cosign policy command has been removed (#2846)
33. 2.0.0 Feb 24, 2023 · release notes

    Cosign 2.0 adds identity-based signing, transparency logs, blob attestations, and trusted timestamping.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.0.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout 2.0.0

    • Identity-based (keyless) signing now defaults to true without requiring COSIGN_EXPERIMENTAL=1
    • Artifact signatures upload to the Rekor transparency log by default; controlled via --tlog-upload=false
    • Verification requires identity flags: --certificate-identity and --certificate-oidc-issuer
    • Fulcio certificate issuance now supports self-managed keys (--issue-certificate=true with --key or --sk)
    • Experimental trusted timestamping via --timestamp-server-url for container signing

    +3 more show less

    • Blob attestation supported with new cosign attest-blob command
    • CLI flags can be set via environment variables (e.g., COSIGN_CERTIFICATE_IDENTITY)
    • --offline=true disables the Rekor fallback during verification

    8 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !COSIGN_EXPERIMENTAL=1 is no longer required for identity-based signing
    • !Artifact signatures now upload to Rekor by default; use --tlog-upload=false to skip
    • !Verification now requires --certificate-identity and --certificate-oidc-issuer
    • !--certificate-email has been removed; use --certificate-identity instead
    • !SCT verification is now on by default for Fulcio certificates; use --insecure-ignore-sct=true to skip
    • !DSSE support in verify-blob removed; use verify-blob-attestation
    • !SIGSTORE_TRUST_REKOR_API_PUBLIC_KEY env var removed; use SIGSTORE_REKOR_PUBLIC_KEY or TUF
    • !verify-blob no longer searches for a certificate; must provide --certificate or --bundle
    • !Attestation types now use RFC 3986 compliant URIs (e.g., adding https://)
    • !cosign attest --type vuln envelope changed to comply with in-toto specification
    • !--force flag removed; use --yes to skip prompts
34. 2.0.0-rc.2 Prerelease Feb 10, 2023 · release notes

    Cosign v2.0.0-rc.2 adds GitHub Enterprise server support for key generation and self-managed Fulcio cert fetching.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.0.0-rc.2 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout 2.0.0-rc.2

    • cosign generate-key-pair now supports GitHub Enterprise servers
    • Added support for fetching Fulcio certificates using a self-managed key

    2 details in Everything

35. 2.0.0-rc.1 Prerelease Jan 27, 2023 · release notes

    cosign 2.0.0-rc.1 adds keyless blob signing, custom Rego messages, and stricter cert verification

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.0.0-rc.1 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout 2.0.0-rc.1

    • verify-blob-attestation gains keyless verification capability
    • Rego evaluation adds support for custom error/warning messages in rules
    • import-key-pair allows custom key names via a new parameter

    3 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !cosign verify now requires --certificate-issuer and --certificate-subject flags; they were previously optional.
36. 2.0.0-rc.0 Prerelease Dec 16, 2022 · release notes

    Cosign 2.0 rc0 adds RFC3161 TSA signing/verification, air-gapped offline verification, and keyless-by-default workflow

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.0.0-rc.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout 2.0.0-rc.0

    • cosign sign now defaults to keyless signing with Fulcio (removes COSIGN_EXPERIMENTAL env var)
    • --tlog-upload flag (default true) replaces deprecated --no-tlog-upload; controls Rekor upload for all commands
    • Supports attestation and blob signing/verification using an RFC3161 time-stamping server (TSA)
    • --offline flag forces offline verification mode

    4 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The COSIGN_EXPERIMENTAL environment variable is removed; the default signing method is now keyless signing with Fulcio
    • !SCT verification behavior defaults to enforcement rather than skipping validation
    • !The --force flag on cosign sign and cosign attest is replaced by --yes to skip confirmation prompts
    • !The --no-tlog-upload flag is removed; use --tlog-upload=false instead (default is now true)
37. v1.13.1 Oct 17, 2022 · release notes

    Adds attest-blob and verify-blob-attestation CLI subcommands for blob attestation workflows

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v1.13.1 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v1.13.1

    └──▷ TRY IT
    Attest a binary blob and save the result directly to a file.
    copy

    $ cosign attest-blob <blob_path> --output-attestation attestation.json

    Verify an in-toto attestation while enforcing a specific certificate identity.
    copy

    $ cosign verify-blob-attestation --cert-identity <subject_alternate_name> <blob_path>

    • Adds the attest-blob CLI subcommand to create attestations for arbitrary blobs
    • Adds the --output-attestation flag to attest-blob to direct output to a file instead of stdout
    • Adds the verify-blob-attestation CLI subcommand to verify in-toto attestation statements for blobs
    • Adds the --cert-identity flag to verify commands to match subject alternate names during verification

    4 details in Everything

38. v1.13.0 Oct 7, 2022 · release notes

    Cosign v1.13.0 adds stdin support for predicate input and Fulcio username identity in SAN

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v1.13.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v1.13.0

    └──▷ TRY IT
    Sign a container image using an SBOMSBOMA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. streamed directly from a previous step without writing to disk.
    copy

    $ cat sbom.json | cosign sign --predicate - quay.io/example/image:latest

    • predicate command now accepts standard input (-) as the input source, enabling pipelines like cat sbom.json | cosign sign --predicate - ...

    1 detail in Everything

39. v1.12.0 Sep 14, 2022 · release notes

    cosign v1.12.0 adds non-ECDSAECDSAThe elliptic-curve signature algorithm behind most TLS certificates, blockchains and many hardware keys. It is one of the algorithms post-quantum signatures are meant to replace. support for verify-blob and Alibaba Cloud integration

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v1.12.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v1.12.0

    • Adds --bundle flag to verify-blob for offline verification via Rekor bundle
    • Expands verify-blob coverage to non-ECDSA key types (e.g. RSARSAThe oldest widely used public-key algorithm, for both encryption and signatures, with security resting on factoring large numbers. A large quantum computer would break it., Ed25519Ed25519A fast elliptic-curve signature scheme with small keys, the default for new SSH keys and common in code signing. It is not quantum-safe.)
    • Adds Alibaba Cloud Container Registry credential helper integration

    3 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !verify-blob with signatures created in keyless mode now requires COSIGN_EXPERIMENTAL=1 or a valid Rekor bundle passed with --bundle for offline verification
40. advisory CVE-2022-36056 Sep 14, 2022 · issue 128
    • CVE-2022-36056: Vulnerabilities with blob verification (CVSSCVSSCommon Vulnerability Scoring System, a method for describing a vulnerability's characteristics and severity. Its score is not the probability that attackers will exploit it. 5.5, affects <=1.11.1)⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
41. v1.11.1 Aug 24, 2022 · release notes

    cosign v1.11.1 adds a reworked fig autocomplete command for improved CLI completion.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v1.11.1 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v1.11.1

    └──▷ USE IT
    Rebuild and enable faster, more accurate autocompletion for the fig shell completion system.
    shell copy

    cosign fig autocomplete

    • feat: Rework fig autocomplete command

    1 detail in Everything

42. v1.11.0 Aug 18, 2022 · release notes

    cosign v1.11.0 adds env subcommand and verifies certificate chain against Fulcio root trust by default

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v1.11.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v1.11.0

    • Adds the env subcommand to root to display environment variable configuration.

    1 detail in Everything

43. advisory CVE-2022-35929 Aug 4, 2022 · issue 128
    • CVE-2022-35929: cosign verify-attestation --type can report a false positive if any attestation exists (CVSSCVSSCommon Vulnerability Scoring System, a method for describing a vulnerability's characteristics and severity. Its score is not the probability that attackers will exploit it. 9.8, affects < 1.10.0)⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
44. v1.10.1 Aug 4, 2022 · release notes

    cosign v1.10.1 adds flags to skip transparency log uploads and pass multiple payloads for attestations

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v1.10.1 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v1.10.1

    └──▷ USE IT
    Sign an image and its attestation without publishing to the public transparency log for private deployments.
    shell copy

    cosign attach attestation --attestation=custom.json --skip-upload IMAGE

    Attach multiple attestation payloads to an image in a single command invocation.
    shell copy

    cosign attach attestation --attestation=payload1.json --attestation=payload2.json IMAGE

    • Adds --skip-upload flag to cosign attach attestation to allow skipping upload to the transparency log
    • Enables passing multiple payloads to cosign attach attestation instead of a single payload

    2 details in Everything

45. v1.10.0 Jul 22, 2022 · release notes

    cosign v1.10.0 adds env subcommand for ambient OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. providers and spdxjson/cyclonedx attestation predicates.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v1.10.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v1.10.0

    • Adds --platform flag to cosign sbom download to select the target architecture
    • Adds --oidc-provider flag to specify which provider to use for ambient credentials
    • Adds spdxjson predicate type for attestations
    • Adds cyclonedx predicate type for attestations
    • Separates RegExp matching of issuer/subject from strict validation in verification

    5 details in Everything

46. v1.9.0 Jun 3, 2022 · release notes

    cosign v1.9.0 adds --oidc-providers-disable flag, Rego policy support for cosigned, and glob matching improvements.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v1.9.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v1.9.0

    • Improves image glob matching by adding support for "**" (PR #1914) and removing regex from image pattern fields (PR #1873)
    • Adds --attachment-tag-prefix flag to the tree command

    2 details in Everything

47. v1.8.0 Apr 27, 2022 · release notes

    cosign v1.8.0 adds --webhook-name/-(validating|mutating)-webhook-name flags, env:// key refs, and parallel policy evaluation

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v1.8.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v1.8.0

    • Allows configuring the webhook name via the --webhook-name flag for single webhooks.
    • Adds --(validating|mutating)-webhook-name flags to configure names for validating and mutating webhooks separately.
    • Enables passing keys via environment variables using env:// refs.

    3 details in Everything

48. v1.7.1 Apr 5, 2022 · release notes

    cosign v1.7.1 adds cosign tree subcommand, certificate chain support for signing/verification, and registry keychain override

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v1.7.1 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v1.7.1

    └──▷ USE IT
    Inspect which images are referenced in a signed container image
    shell copy

    cosign tree <image-ref>

    Sign an image with a specific intermediate certificate chain for trust validation
    shell copy

    cosign sign --key cosign.key --certificate cert.pem --certificate-chain chain.pem <image-ref>

    • Adds cosign tree command to display the image dependency graph
    • Adds --certificate and --certificate-chain flags to sign for intermediate certificate validation
    • Enables overriding the registry keychain used by signing and verification commands

    3 details in Everything

49. v1.6.0 Mar 4, 2022 · release notes

    cosign v1.6.0 adds login, --timeout to sign, SPIFFESPIFFEAn open standard, maintained by the CNCF, for assigning cryptographic identities to workloads in dynamic infrastructure so services can authenticate each other without passwords or static credentials. socket override, TUF root status, enhanced clean, and other types for copy.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v1.6.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v1.6.0

    └──▷ TRY IT
    Authenticate with Fulcio before signing artifacts
    copy

    $ cosign login

    Set a timeout for the signing operation to prevent hangs
    copy

    $ cosign sign --timeout 30s <image>

    Copy artifacts between registries supporting additional media types
    copy

    $ cosign copy <source> <dest>

    • Adds login subcommand for interactive Fulcio login
    • Adds --timeout flag to the sign command
    • Allows overriding the Spiffe socket via an environmental variable
    • Outputs TUF root status with the TUF: Add root status output feature
    • Enhances clean command capability for artifact removal

    +2 more show less

    • Adds fig autocomplete support for CLI completion
    • Extends copy command to support other types beyond images

    7 details in Everything

50. v1.5.1 Jan 31, 2022 · release notes

    cosign v1.5.1 adds DSSE support to verify-blob and exposes default Fulcio/Rekor/oidc URLs.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v1.5.1 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v1.5.1

    • Adds --dsse flag to verify-blob command to support DSSE payloads
    • Exposes default Fulcio, Rekor, and OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. issuer URLs via environment variables

    2 details in Everything

51. 1.5.1 Jan 31, 2022 · release notes

    cosign v1.5.1 adds DSSE support to verify-blob and exposes default Fulcio/Rekor URLs

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 1.5.1 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout 1.5.1

    • verify-blob now supports verifying DSSE envelopes
    • Exposes defaults for fulcio, rekor, and oidc issuer URLs as environment variables

    2 details in Everything

52. v1.5.0 Jan 24, 2022 · release notes

    Cosign v1.5 adds TUF timestamp bundling, PKCS#8 key imports, and ambient credential detection.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v1.5.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v1.5.0

    └──▷ USE IT
    Sign a blob and immediately generate a signed TUF timestamp bundle in the same command.
    shell copy

    cosign sign-blob --bundle sig.txt <file>

    • Bundles a TUF timestamp with the signature output when signing (via --bundle on sign-blob or implied in image attestation).
    • Adds the --bundle flag to cosign sign-blob and cosign verify-blob commands for explicit bundle handling.
    • Supports importing PKCS#8 private keys into the keychain via existing key import workflows.
    • Enables ambient credential detection using SPIFFESPIFFEAn open standard, maintained by the CNCF, for assigning cryptographic identities to workloads in dynamic infrastructure so services can authenticate each other without passwords or static credentials./Spire for keyless signing identities.

    4 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The upload flag for cosign initialize has been removed; the tool no longer prompts for or performs uploads.
53. v1.4.1 Dec 10, 2021 · release notes

    Adds cosign verify-attestation --local-image and initializes TUF root over HTTP

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v1.4.1 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v1.4.1

    └──▷ USE IT
    Download the TUF root from a custom HTTP mirror to configure cosign for use in an air-gapped environment.
    shell copy

    cosign initialize --mirror https://tuf-mirror.example.com/root.json

    Verify the attestations of a container image loaded from a local tar archive without pushing it to a registry.
    shell copy

    cosign verify-attestation --local-image ./my-image.tar

    • cosign initialize --mirror enables fetching the TUF root of trust over HTTP for offline or restricted environments.
    • cosign verify-attestation --local-image supports verifying signed images with attestations directly from a local disk image, removing the need for an OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. registry.
    • Files written via --output-signature and --output-certificate are now created with 0600 permissions by default.

    3 details in Everything

54. v1.4.0 Dec 7, 2021 · release notes

    cosign v1.4.0 adds cosign save/load commands, --replace attestation flag, and disk storage via pkg/oci/layout

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v1.4.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v1.4.0

    └──▷ USE IT
    Persist local copies of a container image and its signature for air-gapped environments or archival.
    shell copy

    cosign save --output-dir ./saved-image <image-ref>
    cosign load --input-dir ./saved-image

    Verify a container image signature stored in a local file using a specific digest algorithm.
    shell copy

    cosign verify --signature sig.sig \
      --signature-digest-algorithm SHA384 \
      <image-ref>

    • Adds cosign save and cosign load commands to store container images and signatures on disk
    • Adds --replace option to cosign attest to overwrite existing attestations
    • Adds pkg/oci/layout package for writing signatures and attestations to local disk storage
    • Adds mutate.AttachFileTo* methods to attach oci.File objects to signed images
    • Adds --signature-digest-algorithm flag to cosign verify to specify signature hash algorithms other than SHA256SHA256A cryptographic hash function that turns data into a fixed 256-bit fingerprint. It is used to check integrity; hashing does not encrypt the original data.

    +5 more show less

    • Adds --signature and --cert flags to cosign verify to accept signatures and certificates from local files or remote URLs
    • Adds URI to cosign verify-blob output for transparency log entry location
    • Adds support for syft format SBOMsSBOMsA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. in cosign attach sbom
    • Enables --output-signature and --output-certificate flags on cosign sign and cosign sign-blob to write outputs to files
    • Updates release binaries to include keyless workflow support

    10 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !cosign releases now generate signatures in keyless experimental mode that do not validate in older versions of cosign; use --fulcio-url=https://fulcio.sigstore.dev to opt out
    • !SignedEntryTimestamp type in pkg is changed from its previous type to []byte
    • !Release binary cosign-linux-pivkey-amd64 is renamed to cosign-linux-pivkey-pkcs11key-amd64
55. v1.3.1 Nov 11, 2021 · release notes

    cosign v1.3.1 adds PKCS11PKCS11The standard programming interface software uses to ask an HSM, smart card or token to sign or decrypt with a key it holds. Supporting it lets a tool keep its keys in hardware. signing support and verify-blob transparency log cert discovery.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v1.3.1 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v1.3.1

    └──▷ TRY IT
    Upload a signature to Rekor with a custom timeout to avoid hangs on slow networks.
    copy

    $ cosign upload signed-image --timeout 120s

    Sign a blob using a hardware token via PKCS11.
    copy

    $ cosign sign-blob --key pkcs11://token=path=/tmp/token.pem id=1234 my-blob.txt

    Verify a blob where the certificate is fetched directly from the transparency log.
    copy

    $ cosign verify-blob --certificate-identity https://github.com/... --certificate-oidc-issuer https://token.actions.githubusercontent.com --signature signature.sig my-blob.txt

    • Adds --timeout flag to the cosign upload command to control the timeout for uploading to Rekor
    • Adds PKCS11 signing support via a new backend option in the --key flag (e.g., pkcs11://...)
    • Enhances verify-blob to automatically find the signing certificate in the transparency log when --certificate-identity or similar identity flags are used

    3 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !cosign.Verify function has been removed; use cosign.VerifyImageSignatures and cosign.VerifyImageAttestations instead.
56. v1.3.0 Nov 3, 2021 · release notes

    Cosign v1.3.0 adds sget CLI, --k8s-keychain flag, webhook digest resolution, and refactors package API.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v1.3.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v1.3.0

    └──▷ USE IT
    Securely download a container image without pulling the full manifest first, useful for CI/CD pipelines where you only need the binary blob.
    shell copy

    sget cosign testimg

    Authenticate to a container registry using Kubernetes service account credentials when running inside a cluster, avoiding manual docker login or secret mounts.
    shell copy

    cosign attach sbom --sbom ./syft.json --image myregistry.io/myapp:v1 --k8s-keychain

    Disable TLS verification when interacting with a self-signed local registry during development or testing.
    shell copy

    cosign upload blob --image myregistry.local/app.tar.gz --allow-insecure-registry

    • Adds sget as a standalone CLI tool in releases for secure container image grabbing
    • Adds --allow-insecure-registry flag to disable TLS verification for self-signed registries
    • Adds --k8s-keychain option to enable ambient registry credentials via the k8schain library
    • New cosigned mutating webhook resolves image tags to digests before admission
    • cosigned validating webhook now rejects image tag references, requiring digest references

    +2 more show less

    • manifest verify (renamed from verify-manifest) supports verifying images in PodSpec, PodSpecTemplate, JobSpecTemplate, and CRDsCRDsA Kubernetes extension that adds a new object type to the cluster, so a tool's configuration is stored, validated and versioned by Kubernetes itself rather than in a file beside it.
    • Adds shell auto-completion support via Cobra CLI migration

    7 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !verify-manifest subcommand is renamed to manifest verify
    • !pkg/cosign/remote.UploadSignature API removed in favor of pkg/oci/remote APIs
    • !cremote.UploadFile removed in favor of static.NewFile and remote.Write
57. v1.2.0 Sep 14, 2021 · release notes

    cosign v1.2.0 adds dockerfile verify, URL-based blob verification, -cert-email flag, and remote attachment signing/verification

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v1.2.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v1.2.0

    └──▷ HOW TO FIND IT
    Verify a Dockerfile's signature using the new subcommand structure.
    📍cosign dockerfile verify --key <public-key> Dockerfile
    Verify a blob signature fetched directly from a remote URL without downloading it first.
    📍cosign verify-blob --key <public-key> https://example.com/signature.txt
    Sign a container image while enforcing that the identity certificate contains a specific email address.
    📍cosign sign --key <key> -cert-email user@example.com gcr.io/my-project/image:tag
    Sign an SBOMSBOMA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. or other artifact as an attachment to the image signature.
    📍cosign sign-attachment --key <key> sbom spdx gcr.io/my-project/image:tag sbom.json
    Verify an SBOM attachment that was signed as part of the image's transparency log entry.
    📍cosign verify-attachment --key <public-key> sbom spdx gcr.io/my-project/image:tag
    • Move verify-dockerfile to dockerfile verify subcommand for Dockerfile verification.
    • Allow verify-blob to fetch signatures directly from URLs with a new source argument.
    • Add -cert-email flag to cosign sign to require an email match in the fulcio certificate.
    • Add sign-attachment and verify-attachment subcommands for signing and verifying artifacts like SBOMsSBOMsA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. and attestations.
    • Support GCP environments without workload identityworkload identityAn identity assigned to software, such as a service or container, rather than a person. It lets the workload authenticate and receive permissions without sharing a user's credentials. (GCB) by detecting and using ambient OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. tokens automatically.

    5 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The verify-dockerfile command is removed; users must now use the dockerfile verify subcommand instead.
58. v1.1.0 Aug 25, 2021 · release notes

    Adds verify-manifest, cosign init, -type flag for well-known attestation types

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v1.1.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v1.1.0

    └──▷ TRY IT
    Verify a Kubernetes manifest signed with cosign
    copy

    $ cosign verify-manifest --key <KEY> image:tag

    Initialize the local Sigstore TUF root metadata store
    copy

    $ cosign init

    Create an attestation with a well-known type like in-toto
    copy

    $ cosign attest --type in-toto.io/slsa-provenance/v0.2 image:tag

    • Adds verify-manifest subcommand to verify Kubernetes manifest signatures in CLI
    • Adds cosign init command to setup the local TUF root metadata repository
    • Adds -type flag to attest command for specifying well-known attestation types
    • Adds timestamp support to Cosign's custom In-Toto predicate

    4 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The -attestation flag in attest is renamed to -predicate
59. v1.0.0 Jul 28, 2021 · release notes

    Cosign v1.0.0 introduces the attest command, -cert flag on sign, and environment variable COSIGN_ROOT for custom Fulcio CA files.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v1.0.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout v1.0.0

    └──▷ USE IT
    Add a signature certificate explicitly when signing a blob.
    shell copy

    cosign sign -key cosign.key -cert cert.pem blob.txt

    Create an attestation for a container image.
    shell copy

    cosign attest --key cosign.key --predicate predicate.json myimage:latest

    • cosign will now send its version string as part of the user-agent when interacting with a container registry
    • Added the attest command to cosign
    • Added -cert flag to sign to allow the explicit addition of a signature certificate
    • Files containing certificates for custom Fulcio endpoints can now be specified via the COSIGN_ROOT environment variable

    4 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !--fulcio-server is renamed to --fulcio-url
    • !The default HSMHSMA tamper-resistant device that generates and stores cryptographic keys and performs operations with them, so the private key never leaves the hardware. Cloud KMS services run on fleets of them. key slot changes from authentication to signature
60. 0.6.0 Jul 12, 2021 · release notes

    cosign v0.6.0 adds verify-dockerfile, SBOMSBOMA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. attach/download, AWS KMSAWS KMSAWS Key Management Service, Amazon's hosted service for creating and controlling cryptographic keys, giving cyber tools a durable, audited place to encrypt data without managing raw key material themselves., and flags for security key policies.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 0.6.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout 0.6.0

    └──▷ USE IT
    Verify a Dockerfile against its image signatures locally
    shell copy

    cosign verify-dockerfile --key cosign.pub Dockerfile

    Attach an SBOM to a signed container image
    shell copy

    cosign attach sbom --sbom cyclonedx.json cosigned-image:latest

    Download an SBOM from a container image that has one attached
    shell copy

    cosign download sbom cosigned-image:latest -o output.json

    • Adds --slot, --pin, and touch policy flags to control hardware security keys
    • Adds cosign verify-dockerfile command to verify container image Dockerfiles
    • Adds SBOM support via cosign attach sbom and the new cosign download sbom command
    • Adds support for AWS KMSKMSA managed service that creates, stores, rotates and controls access to encryption keys, usually backed by HSMs. Applications ask it to encrypt or decrypt rather than holding keys themselves. as a signing key provider

    4 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !cosign upload-blob is renamed to cosign upload blob
    • !cosign attach signature replaces the old cosign upload command
    • !cosign download signature replaces the old cosign download command
61. 0.5.0 Jun 4, 2021 · release notes

    Adds cosign copy, cosign clean, recursive signing -r flag, and k8s secret key generation

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 0.5.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout 0.5.0

    └──▷ TRY IT
    Copy an image and its signatures from one registry to another.
    copy

    $ cosign copy source:image:v1 dest:registry.io/image:v1

    Sign all components of a multi-arch image in one command.
    copy

    $ cosign sign -r gcr.io/project/image:v1

    Remove all signatures associated with a specific image.
    copy

    $ cosign clean gcr.io/project/image:v1

    Generate a key pair and store it directly as a Kubernetes Secret.
    copy

    $ cosign generate-key-pair -k8s

    • Added cosign copy to easily move images and signatures between repositories
    • Added -r flag to cosign sign for recursively signing multi-arch images
    • Added cosign clean to delete signatures for an image
    • Added -k8s flag to cosign generate-key-pair to create a Kubernetes secret

    4 details in Everything

62. 0.4.0 May 5, 2021 · release notes

    Cosign v0.4.0 adds offline Rekor verification and Hashicorp Vault KMSKMSA managed service that creates, stores, rotates and controls access to encryption keys, usually backed by HSMs. Applications ask it to encrypt or decrypt rather than holding keys themselves. support

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 0.4.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout 0.4.0

    └──▷ BREAKING ON UPGRADE

    • !Signature image manifest now uses OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. mediaTypes instead of previous format
    • !Signature image tag suffix changed from .cosign to .sig
63. 0.3.0 Apr 19, 2021 · release notes

    cosign 0.3.0 adds -output-file, KMSKMSA managed service that creates, stores, rotates and controls access to encryption keys, usually backed by HSMs. Applications ask it to encrypt or decrypt rather than holding keys themselves. URLs in -key, Yubikey/PIV support, and multi-image signing.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 0.3.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout 0.3.0

    └──▷ USE IT
    Sign a container image and save the signature payload to a specific file.
    shell copy

    cosign sign -output-file sig.json <image>

    Use a KMS URL directly via the -key flag without needing a separate KMS-specific flag.
    shell copy

    cosign sign -key kms://<key-url> <image>

    • Adds -output-file flag to write command output to a specific file
    • Updates -key flag to accept kms references and URLs (replacing the dedicated kms flag)
    • Adds Yubikey/PIV hardware support for key operations
    • Enables signing and verifying multiple images in a single invocation

    4 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The dedicated kms flag is removed; users must now use the -key flag with kms references.
64. 0.2.0 Mar 29, 2021 · release notes

    cosign 0.2.0 adds COSIGN_PASSWORD support, KMSKMSA managed service that creates, stores, rotates and controls access to encryption keys, usually backed by HSMs. Applications ask it to encrypt or decrypt rather than holding keys themselves. blob signing, public-key extraction, and COSIGN_REPOSITORY config

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 0.2.0 https://github.com/sigstore/cosign.git
    # already have the repo? check out this version:
    $ git checkout 0.2.0

    └──▷ USE IT
    Pass a private key password without interactive prompts for CI/CD automation
    shell copy

    COSIGN_PASSWORD=secret cosign sign --key cosign.key <image>

    • COSIGN_PASSWORD environment variable to pass private key passwords directly

    1 detail in Everything