# CVE-2026-22703: GO-2026-4309 - Cosign verification accepts any valid Rekor entry under certain conditions in github.com/sigstore/cosign

Source: https://junglewise.ai/threats/cve-2026-22703-cosign-verification-accepts-any-valid-rekor-entry-under-certain  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-01-13  
License: CC BY 4.0 with a link back

CVE-2026-22703 · Severity: low · CVSS 3.1 · Published 2026-01-13

Cosign verification accepts any valid Rekor entry under certain conditions in github.com/sigstore/cosign

Technologies: [github.com/sigstore/cosign (Go)](https://junglewise.ai/threats/technologies/github-com-sigstore-cosign), [github.com/sigstore/cosign/v2 (Go)](https://junglewise.ai/threats/technologies/github-com-sigstore-cosign-v2), [github.com/sigstore/cosign/v3 (Go)](https://junglewise.ai/threats/technologies/github-com-sigstore-cosign-v3). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2026-22703 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-22703 being exploited in the wild.

**How severe is CVE-2026-22703?** Low severity, with a CVSS score of 3.1, published 13 January 2026.

**Which products and versions are affected?** github.com/sigstore/cosign (Go) SEMVER:introduced=0; github.com/sigstore/cosign/v2 (Go) SEMVER:introduced=0,fixed=2.6.2; github.com/sigstore/cosign/v3 (Go) SEMVER:introduced=0,fixed=3.0.4.

**Is there a fix for CVE-2026-22703?** Yes. github.com/sigstore/cosign/v2 (Go): upgrade to 2.6.2 or later; github.com/sigstore/cosign/v3 (Go): upgrade to 3.0.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-22703?** Check whether you run github.com/sigstore/cosign (Go), github.com/sigstore/cosign/v2 (Go) or github.com/sigstore/cosign/v3 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/sigstore/cosign/v2 (Go): upgrade to 2.6.2 or later

  ```sh
  go get github.com/sigstore/cosign/v2@v2.6.2
  ```

- github.com/sigstore/cosign/v3 (Go): upgrade to 3.0.4 or later

  ```sh
  go get github.com/sigstore/cosign/v3@v3.0.4
  ```


## Affected products

- github.com/sigstore/cosign (Go) SEMVER:introduced=0
- github.com/sigstore/cosign/v2 (Go) SEMVER:introduced=0,fixed=2.6.2
- github.com/sigstore/cosign/v3 (Go) SEMVER:introduced=0,fixed=3.0.4

## Identifiers

- CVE-2026-22703
- GHSA-whqx-f9j3-ch6m
- GO-2026-4309

## Related threats

- [Sigstore Cosign validation bypass in verify-blob-attestation](https://junglewise.ai/threats/cve-2026-39395-sigstore-cosign-validation-bypass-in-verify-blob-attestation)
- [Cosign considered signatures valid with expired intermediate certificates when transparency log verification is skipped](https://junglewise.ai/threats/cve-2026-24122-cosign-considered-signatures-valid-with-expired-intermediate)
- [GO-2024-2719 - Cosign malicious artifacts can cause machine-wide DoS in github.com/sigstore/cosign](https://junglewise.ai/threats/cve-2024-29903-cosign-malicious-artifacts-can-cause-machine-wide-dos)
- [GO-2024-2718 - Cosign malicious attachments can cause system-wide denial of service in github.com/sigstore/cosign](https://junglewise.ai/threats/cve-2024-29902-cosign-malicious-attachments-can-cause-system-wide-denial-of)
- [GO-2022-0998 - Improper blob verification in github.com/sigstore/cosign](https://junglewise.ai/threats/cve-2022-36056-cosign-bundle-can-be-crafted-to-successfully-verify-a-blob-even)