CVE-2026-47192

kas's late signature validation may allow unnoticed repository manipulations

Workarounds

Pin the expected signature key via its fingerprint, also when storing it as file in a repository.

So far, kas checks out and processes repositories regarding configuration includes prior to validating signatures of those repositories. This may allow to replace on original repository with one under the control of an attacker under very specific conditions.

First of all, the attacker must have gained control of a repository that a kas file of the victim is referencing. Furthermore, the following conditions must be fulfilled:

• the victim's kas configuration must include a configuration file from the attacked repository
• the repository state is referenced by tag, and no commit ID is specified (this is triggering a warning, though)
• the key used for validating the tag or commit signature is stored as file in a repository
• no fingerprint for the key is specified
• the _source_dir key must not be set by the victim when calling kas (e.g. by avoiding a local .config.yaml)

Given these conditions, the attacker could modify the included kas configuration in way that the key used to validate the tag signature of the attacker's repository could be replaced by an attacker-chosen key.

No other exploit possibilities have been identified so far, but this does not rule out that those may exist.

Kodem intelligence

Already deployed Kodem?

The vulnerability was introduced with a2480fe59b6421eb96cf3bd86527ae6e412a331e, commit https://github.com/siemens/kas/commit/5b2114becfc154b16ef496d24f8c2191a2297f57 is resolving this issue. A misuse of _source_dir is resolved by commit https://github.com/siemens/kas/commit/c443c0a1fd0f9bd6a689a44d95a252085fc6da88. Shadowing a commit by a branch of the same name is described in advisory https://github.com/siemens/kas/security/advisories/GHSA-qjwp-hrq6-r26r and is addressed by commit https://github.com/siemens/kas/commit/4cb4a3d01122ffaec9feaae768a5814092f6f9b5. All patches have been released along with kas version 5.3.

1. What is CVE-2026-47192? CVE-2026-47192 is a low-severity security vulnerability in kas (pip), affecting versions >= 4.8, < 5.3. It is fixed in 5.3.
2. Which versions of kas are affected by CVE-2026-47192? kas (pip) versions >= 4.8, < 5.3 is affected.
3. Is there a fix for CVE-2026-47192? Yes. CVE-2026-47192 is fixed in 5.3. Upgrade to this version or later.
4. Is CVE-2026-47192 exploitable, and should I be worried? Whether CVE-2026-47192 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2026-47192 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2026-47192? Upgrade kas to 5.3 or later.

Other vulnerabilities in kas