CVE-2026-22703Medium· 5.5▾ SunlitA data verification flaw has been discovered in the golang cosign library. 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…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 30.3 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Aug 24.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CSAF
0.09%
Last analysed / modified upstream
0.09% → 0.1%
A data verification flaw has been discovered in the golang cosign library. 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.
github.com/sigstore/cosign: Cosign verification accepts any valid Rekor entry under certain conditions — rated Moderate by Red Hat. Released 2026-01-10, updated 2026-09-23.
Affected:
No fix planned:
Fix deferred
Workarounds / mitigations:
Affected packages:
github.com/sigstore/cosign/v3 < 3.0.4github.com/sigstore/cosign/v2 < 2.6.2Patched in:
github.com/sigstore/cosign/v3 3.0.4github.com/sigstore/cosign/v2 2.6.2Connected by shared product, vendor, weakness, or advisory.
CVE-2026-23991Medium· 5.9github.com/theupdateframework/go-tuf/v2: go-tuf client DoS via malformed server response (CVE-2026-23991)
CVE-2026-25542Medium· 6.5github.com/tektoncd/pipeline: Tekton Pipelines: Security bypass due to regular expression matching flaw (CVE-2026-25542)
CVE-2026-33022Medium· 6.5github.com/tektoncd/pipeline: Tekton Pipelines: Denial of Service via long resolver names (CVE-2026-33022)
CVE-2026-58443Critical· 9.6code.gitea.io/gitea: Gitea: Unauthorized update of private pull request branches via public-only tokens (CVE-2026-58443)
CVE-2026-115877Medium· 5.4twisted: Twisted: HTTP request smuggling via improper header delimiter handling (CVE-2026-115877)
CVE-2026-114140High· 7.8nbconvert: nbconvert: arbitrary file write via path traversal in ExtractOutputPreprocessor (CVE-2026-114140)