Invalid artifact acceptance via fail-open blob verification
Published Sep 14, 2022 · Updated Apr 22, 2025
Improper signature verification in Sigstore Cosign before 1.12.0 allows local users to make verify-blob accept invalid artifacts. The verify-blob paths fail open when bundle fields do not bind the signature, identity constraints are ignored, or Rekor validation errors trigger early success. Exploitation requires control of verification inputs and undermines artifact-integrity decisions without directly disclosing data or interrupting the service.
Summary
What happened
Improper signature verification in Sigstore Cosign before 1.12.0 allows local users to make verify-blob accept invalid artifacts. The verify-blob paths fail open when bundle fields do not bind the signature, identity constraints are ignored, or Rekor validation errors trigger early success. Exploitation requires control of verification inputs and undermines artifact-integrity decisions without directly disclosing data or interrupting the service.
The record
- CVE
- CVE-2022-36056
- Published
- Sep 14, 2022
- Updated
- Apr 22, 2025
- Vendor
- Sigstore
- Product
- Cosign
- Classifications
- CWE-347, T1553.002
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 14, 2022CVE publishedPublication date reported by the CVE source.
- 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.
- Affected versionversion=< 1.12.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
Public exploit references
- Sigstore crafted-bundle verification examplesproof of concept · demonstrated
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