kas considers a branch of the same name as a valid commit when only a SHA value is supplied, which undermines the integrity check that the configuration file defines. The flaw allows a repository that has been taken over by an attacker to present a malicious branch that satisfies the commit ID requirement. This could enable the injection of malicious code or the deployment of an unintended repository state. The overall impact is low, reflected in the CVSS score of 2.1, because the attacker must control the target repository and create a branch with the same name; a direct code‑execution vector is not present.

The issue affects Siemens KAS tools before version 5.3. Users running KAS 5.0, 5.1, or 5.2 are susceptible; later releases have been patched.

The CVSS score of 2.1 indicates a low severity. EPSS data is unavailable, and the vulnerability is not listed in CISA KEV, suggesting limited active exploitation. The likely attack scenario requires the attacker to control or compromise the source repository and create a new branch with the same name, after which kas will mistakenly treat the branch tip as the validated commit.