The kas tool for bitbake-based projects, starting from version 4.8 and prior to 5.3, improperly verifies cryptographic signatures by processing repository configurations before signature validation. This can allow an attacker who controls a referenced repository and meets several specific conditions—such as the victim's kas configuration including a file from the attacker-controlled repository, referencing repository state by tag without commit ID, storing the key as a file without specifying a fingerprint, and not setting the _source_dir key—to replace the original repository with a malicious one. No other exploitation methods are currently identified. The vulnerability is addressed in kas version 5.3, and pinning the signature key by fingerprint is advised as a workaround.

An attacker with control over a repository referenced by a victim's kas configuration could replace the original repository with a malicious one under very specific conditions. This could lead to the victim unknowingly processing attacker-controlled configuration files. The impact is limited by the complexity of required conditions and the low CVSS score (2.1), indicating low severity.

A fix is available in kas version 5.3. Users should upgrade to version 5.3 or later to remediate this vulnerability. As a workaround, users can pin the expected signature key by its fingerprint even when the key is stored as a file in a repository. This prevents the attacker from substituting the key used for signature validation. No other mitigations are specified.