Quick answers
- Is CVE-2026-47191 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47191 being exploited in the wild.
- How severe is CVE-2026-47191?
- Medium severity, with a CVSS score of 4, published 1 June 2026.
- Which products and versions are affected?
- kas (PyPI) < 5.3, ECOSYSTEM:introduced=0,fixed=5.3.
- Is there a fix for CVE-2026-47191?
- Yes. kas (PyPI): upgrade to 5.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47191 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-47191?
- Check whether you run kas (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- kas (PyPI): upgrade to 5.3 or later
pip install "kas>=5.3"
Technical details
A vulnerability in Siemens kas (prior to version 5.3) allows for the substitution of a git commit with a branch of the same name. When kas performs a checkout using a commit ID (SHA-1 or SHA-256) for integrity validation, it does not explicitly force the reference to be treated as a commit object. An attacker who has gained control over a referenced repository can create a branch named with the hex string of a valid commit hash. Because git checkout prioritizes or accepts branch names that match the hash string, kas may check out the head of the malicious branch instead of the specific immutable commit. This issue is mitigated by appending '^{commit}' to the reference during checkout to ensure only commit objects are resolved.
Affected products
- Siemens kas < 5.3
Identifiers
- CVE-2026-47191
- GHSA-qjwp-hrq6-r26r
- PYSEC-2026-2544
Timeline
- 2026-05-27: disclosed: Initial publication by Siemens
- 2026-06-01: advisory: GitHub Advisory published
- 2026-06-01: patched: Released in version 5.3