The vulnerability in kas causes the tool to validate repository signatures only after it has checked out and processed the repositories. This late validation can let an attacker, who gains control of a repository that a kas file references, replace the original repository with a malicious version under very specific conditions. The attacker must have control over the referenced repository, the kas configuration must include a configuration file from that repository, the repository state must be referenced by tag without a specific commit ID, the validation key must be stored as a file rather than being fingerprint‑verified, and the _source_dir key must not be set by the victim. The attacker can then modify the configuration so that the key used to validate the tag signature is swapped for an attacker‑chosen key, allowing unnoticed repository manipulation. No other exploit paths have been discovered, but the possibility of additional attacks is not excluded.

The issue affects Siemens’ kas tool, specifically versions 4.8 through 5.3 (exclusive of 5.3). A patch was released in kas version 5.3 that addresses the late signature validation flaw.

The CVSS score is 2.1, indicating a low severity; the EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog, implying a limited likelihood of widespread exploitation. However, because the exploit requires precise conditions—such as an external repository reference via tag and the absence of a local .config.yaml—the attack vector is highly constrained. If an attacker meets those prerequisites, they could manipulate the kas configuration and compromise downstream builds or deployments, potentially leading to unintended code execution or supply‑chain tampering. In practice, the risk remains low but non‑negligible for environments that load external config files without strict commit pinning or key fingerprint verification.