Vulnerabilities in pkg:golang/github.com/sigstore/cosign/v3

PACKAGE
Advisory Identifier: GHSA-whqx-f9j3-ch6m
Advisory Summary

CVE-2026-22703 is a MODERATE (CVSS 5.5) cosign verification accepts any valid vulnerability (CWE-345: Insufficient Verification of Data Authenticity) affecting Github.com/sigstore/cosign/v3 libraries in the Go ecosystem. The issue involves cosign verification accepts any valid rekor entry under certain conditions. Remediation is available by upgrading affected packages to version 3.0.4, 2.6.2.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/sigstore/cosign/v3

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/sigstore/cosign/v3. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-whqx-f9j3-ch6m CVE-2026-22703 MODERATE Cosign verification accepts any valid Rekor entry under certain conditions

CVE-2026-22703 at a Glance

CVE Identifier CVE-2026-22703
GHSA Identifier GHSA-whqx-f9j3-ch6m
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-345: Insufficient Verification of Data Authenticity
Affected Product Github.com/sigstore/cosign/v3
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 5.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-22703

To remediate this vulnerability, upgrade all affected Github.com/sigstore/cosign/v3 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/sigstore/cosign/v3 fixed: 3.0.4
Upgrade github.com/sigstore/cosign/v3 to 3.0.4
github.com/sigstore/cosign/v2 fixed: 2.6.2
Upgrade github.com/sigstore/cosign/v2 to 2.6.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/sigstore/cosign/v3

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-22703, inspect your project dependencies for Github.com/sigstore/cosign/v3:

inspect dependencies for github.com/sigstore/cosign/v3

Analyze the terminal output to locate any version of Github.com/sigstore/cosign/v3 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.0.4), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-345: Insufficient Verification of Data Authenticity, where the product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. In Github.com/sigstore/cosign/v3, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact A 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 vulnerability only affects users that provide a trusted root via `--trusted-root` or when fetched automatically from a TUF repository, when no trusted key material is provided via `SIGSTORE_REKOR_PUBLIC_KEY`. When using the default flag values in Cosign v3 to sign and verify (`--use-signing-config=true` and `--new-bundle-format=true` for signing, `--new-bundle-format=true` for verification), users are unaffected. Cosign v2 users are affected using the default flag values. This issue had previously been fixed in https://github.com/sigstore/cosign/security/advisories/GHSA-8gw7-4j42-w388 but recent refactoring caused a regression. We have added testing to prevent a future regression. #### Steps to Reproduce ``` echo blob > /tmp/blob cosign sign-blob -y --new-bundle-format=false --bundle /tmp/bundle.1 --use-signing-config=false /tmp/blob cosign sign-blob -y --new-bundle-format=false --bundle /tmp/bundle.2 --use-signing-config=false /tmp/blob jq ".rekorBundle |= $(jq .rekorBundle /tmp/bundle.2)" /tmp/bundle.1 > /tmp/bundle.3 cosign verify-blob --bundle /tmp/bundle.3 --certificate-identity-regexp='.*' --certificate-oidc-issuer-regexp='.*' /tmp/blob ``` ### Patches Upgrade to Cosign v2.6.2 or Cosign v3.0.4. This does not affect Cosign v1. ### Workarounds You can provide trusted key material via a set of flags under certain conditions. The simplest fix is to upgrade to the latest Cosign v2 or v3 release. Note that the example below works for `cosign verify`, `cosign verify-blob, `cosign verify-blob-attestation`, and `cosign verify-attestation`. ``` SIGSTORE_REKOR_PUBLIC_KEY=<path to Rekor pub key> cosign verify-blob --use-signing-config=false --new-bundle-format=false --bundle=<path to bundle> <artifact> ```

CVE-2026-22703 Affected Github.com/sigstore/cosign/v3 Versions

2 component(s)
Fixed Versions:
3.0.42.6.2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/sigstore/cosign/v3
Go
< 3.0.4
3.0.4
github.com/sigstore/cosign/v2
Go
< 2.6.2
2.6.2

References

Frequently Asked Questions

What is CVE-2026-22703?
CVE-2026-22703 is a security vulnerability in Github.com/sigstore/cosign/v3 involving Cosign verification accepts any valid Rekor entry under certain conditions under CWE-345: Insufficient Verification of Data Authenticity.
Which Github.com/sigstore/cosign/v3 versions are affected?
Affected versions include releases prior to 3.0.4, 2.6.2 across affected packages: github.com/sigstore/cosign/v3, github.com/sigstore/cosign/v2.
What version fixes CVE-2026-22703?
Upgrading to 3.0.4, 2.6.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/sigstore/cosign/v3 affected?
Yes, github.com/sigstore/cosign/v3 is affected in releases prior to 3.0.4. Upgrade your dependency to 3.0.4 or later.
Is github.com/sigstore/cosign/v2 affected?
Yes, github.com/sigstore/cosign/v2 is affected in releases prior to 2.6.2. Upgrade your dependency to 2.6.2 or later.
What is the CVSS score of CVE-2026-22703?
CVE-2026-22703 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N.
What CWE is associated with CVE-2026-22703?
CVE-2026-22703 is classified under CWE-345: Insufficient Verification of Data Authenticity (The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.).
How can I check Go dependencies for CVE-2026-22703?
Run the dependency tree command: 'inspect dependencies for github.com/sigstore/cosign/v3'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-whqx-f9j3-ch6m",
  "modified" : "2026-01-13T14:58:50Z",
  "published" : "2026-01-13T14:58:50Z",
  "aliases" : [ "CVE-2026-22703" ],
  "summary" : "Cosign verification accepts any valid Rekor entry under certain conditions",
  "details" : "### Impact\n\nA 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.\n\nThis vulnerability only affects users that provide a trusted root via `--trusted-root` or when fetched automatically from a TUF repository, when no trusted key material is provided via `SIGSTORE_REKOR_PUBLIC_KEY`. When using the default flag values in Cosign v3 to sign and verify (`--use-signing-config=true` and `--new-bundle-format=true` for signing, `--new-bundle-format=true` for verification), users are unaffected. Cosign v2 users are affected using the default flag values.\n\nThis issue had previously been fixed in https://github.com/sigstore/cosign/security/advisories/GHSA-8gw7-4j42-w388 but recent refactoring caused a regression. We have added testing to prevent a future regression.\n\n#### Steps to Reproduce\n\n```\necho blob > /tmp/blob\ncosign sign-blob -y --new-bundle-format=false --bundle /tmp/bundle.1 --use-signing-config=false /tmp/blob\ncosign sign-blob -y --new-bundle-format=false --bundle /tmp/bundle.2 --use-signing-config=false /tmp/blob\njq \".rekorBundle |= $(jq .rekorBundle /tmp/bundle.2)\" /tmp/bundle.1 > /tmp/bundle.3\ncosign verify-blob --bundle /tmp/bundle.3 --certificate-identity-regexp='.*' --certificate-oidc-issuer-regexp='.*' /tmp/blob\n```\n\n### Patches\n\nUpgrade to Cosign v2.6.2 or Cosign v3.0.4. This does not affect Cosign v1.\n\n### Workarounds\n\nYou can provide trusted key material via a set of flags under certain conditions. The simplest fix is to upgrade to the latest Cosign v2 or v3 release.\n\nNote that the example below works for `cosign verify`, `cosign verify-blob, `cosign verify-blob-attestation`, and `cosign verify-attestation`.\n\n```\nSIGSTORE_REKOR_PUBLIC_KEY=<path to Rekor pub key> cosign verify-blob --use-signing-config=false --new-bundle-format=false --bundle=<path to bundle> <artifact>\n```",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/sigstore/cosign/v3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.0.4"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.0.3"
    }
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/sigstore/cosign/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.6.2"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2.6.1"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/sigstore/cosign/security/advisories/GHSA-whqx-f9j3-ch6m"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-22703"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/sigstore/cosign/pull/4623"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/sigstore/cosign/commit/6832fba4928c1ad69400235bbc41212de5006176"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/sigstore/cosign"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-345" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-01-13T14:58:50Z",
    "nvd_published_at" : "2026-01-10T07:16:03Z"
  }
}