Improper Verification of Cryptographic Signature Affecting kas package, versions [4.8,5.3)
Threat Intelligence
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-PYTHON-KAS-17670578
- published29 Jun 2026
- disclosed4 Jun 2026
- creditUnknown
Introduced: 4 Jun 2026
NewCVE-2026-47192 (opens in a new tab)How to fix?
Upgrade kas to version 5.3 or higher.
Overview
kas is a Setup tool for bitbake based projects
Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature through improper signature validation during repository configuration includes. An attacker can manipulate repository contents by gaining control of a referenced repository and meeting all of the following conditions: the configuration includes a file from the attacked repository, the repository state is referenced by tag without a commit ID, the key for validating the tag or commit signature is stored as a file in a repository, no fingerprint for the key is specified, and the _source_dir key is not set by the victim. This is only exploitable if all these specific conditions are met.
Workaround
This vulnerability can be mitigated by pinning the expected signature key via its fingerprint, even when storing it as a file in a repository.