Improper Verification of Cryptographic Signature Affecting github.com/kyverno/kyverno/pkg/cosign package, versions <1.14.0-alpha.1
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-GOLANG-GITHUBCOMKYVERNOKYVERNOPKGCOSIGN-9513020
- published25 Mar 2025
- disclosed24 Mar 2025
- creditfrgt10cs
Introduced: 24 Mar 2025
CVE-2025-29778 Â (opens in a new tab)How to fix?
Upgrade github.com/kyverno/kyverno/pkg/cosign to version 1.14.0-alpha.1 or higher.
Overview
Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature in the matchSignatures() function in cosign.go, which does not check for subjectRegExp or issuerRegExp values during artifact signature verification. An attacker can deploy unauthorized Kubernetes resources. This is only exploitable if the attacker has access to a private key of any certificate in the certificate chain trusted by cosign, access to a container registry to push artifact images, and permissions to deploy artifacts.