vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2022-23649

Improper Certificate Validation in Cosign

LOW
3.3
CVSS Score
Published: February 18, 2022 at 09:30 PM UTC
Updated: June 17, 2026 at 04:30 AM UTC
1 product affected across 1 vendorCosign

Using cosign by sigstore?

Get instant alerts when new vulnerabilities affect cosign - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
LOW3.3
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

Cosign provides container signing, verification, and storage in an OCI registry for the sigstore project. Prior to version 1.5.2, Cosign can be manipulated to claim that an entry for a signature exists in the Rekor transparency log even if it doesn't. This requires the attacker to have pull and push permissions for the signature in OCI. This can happen with both standard signing with a keypair and "keyless signing" with Fulcio. If an attacker has access to the signature in OCI, they can manipulate cosign into believing the entry was stored in Rekor even though it wasn't. The vulnerability has been patched in v1.5.2 of Cosign. The `signature` in the `signedEntryTimestamp` provided by Rekor is now compared to the `signature` that is being verified. If these don't match, then an error is returned. If a valid bundle is copied to a different signature, verification should fail. Cosign output now only informs the user that certificates were verified if a certificate was in fact verified. There is currently no known workaround.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Cosign· Sigstore
95%
v < 1.5.2
Affected range stops below 1.5.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (2)

x_refsource_MISCPatchThird Party Advisory
Source: [email protected]
https://github.com/sigstore/cosign/commit/96d410a6580e4e81d24d112a0855c70ca3fb5b49
x_refsource_CONFIRMThird Party Advisory
Source: [email protected]
https://github.com/sigstore/cosign/security/advisories/GHSA-ccxc-vr6p-4858

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

3.3LOWGitHub_M
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
LOW
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-295

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card