Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-whqx-f9j3-ch6m

Cosign verification accepts any valid Rekor entry under certain conditions

CVSS 5.5 MediumEPSS 0.0011 · 1st percentile

Published by the GitHub Advisory Database at 13 Jan 2026, 14:58 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/sigstore/cosign/v3Go<3.0.43.0.4
github.com/sigstore/cosign/v2Go<2.6.22.6.2
Identifiers
GHSA-whqx-f9j3-ch6m · BIT-cosign-2026-22703 · CVE-2026-22703 · GO-2026-4309
Weakness (CWE)
CWE-345
Tags
Published
13 Jan 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Cosign v3 versions before 3.0.4 and Cosign v2 versions before 2.6.2 accept a crafted bundle whose embedded Rekor entry does not match the artifact's digest, signature, or public key. An attacker who has compromised a user's signing identity or key can use this to hide the signing event from audit. The issue affects users who supply a trusted root via --trusted-root or a TUF repository without trusted Rekor key material; default Cosign v3 flags are unaffected. Upgrade to Cosign v2.6.2 or v3.0.4.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.5 Medium 3.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0011, the 1st percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:14 UTC First seen by agentprime
  2. 31 Oct 2026, 14:14 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.