CVE-2022-35929Public exploitNetwork attack vector

False attestation validation via empty predicate match

Published Aug 4, 2022 · Updated Apr 22, 2025

Improper attestation verification in Sigstore Cosign before 1.10.1 allows attackers to obtain a false-positive validation result. VerifyAttestationCommand.Exec treats an empty predicate-type match set as successful after any attestation signature verifies, then prints the verified attestations. Exploitation requires a user to verify an artifact containing a validly signed attestation of another predicate type, allowing a missing required attestation to be trusted as present.

CVSS severity7.1
High
EPSS probability0.65%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper attestation verification in Sigstore Cosign before 1.10.1 allows attackers to obtain a false-positive validation result. VerifyAttestationCommand.Exec treats an empty predicate-type match set as successful after any attestation signature verifies, then prints the verified attestations. Exploitation requires a user to verify an artifact containing a validly signed attestation of another predicate type, allowing a missing required attestation to be trusted as present.

The record

CVE
CVE-2022-35929
Published
Aug 4, 2022
Updated
Apr 22, 2025
Vendor
Sigstore
Product
Cosign
Classifications
CWE-347, T1553
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 4, 2022CVE publishedPublication date reported by the CVE source.
  2. Apr 22, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 1.10.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Sigstore · Cosignversion=< 1.10.1

Published CVSS scores

9.8NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
7.1GitHub, Inc.CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-347Improper Verification of Cryptographic Signature
T1553Subvert Trust Controls

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo