kas
Affected
- introduced
4.8, fixed5.3(ecosystem)
Fixed versions
5.3
Fix
- Fixed version
5.3pip install --upgrade kas==5.3
Advisory
Also known as: CVE-2026-47192, PYSEC-2026-2543
kas's late signature validation may allow unnoticed repository manipulations
Impact
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:
_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.
Patches
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.
Workarounds
Pin the expected signature key via its fingerprint, also when storing it as file in a repository.
Low Basis: The source's own band: LOW
4.8, fixed 5.3 (ecosystem)5.3
5.3pip install --upgrade kas==5.3Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0