CVE-2026-47192
What it is
kas is a setup tool for bitbake based projects. Starting in version 4.8 and prior to version 5.3, 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; and 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. All patches have been released along with kas version 5.3. As a workaround, pin the expected signature key via its fingerprint, also when storing it as file in a repository.
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account, but needs a user to act. Limited direct impact.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 2.1 LOW (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-347
- Record status
- Deferred
Attack profile CVSS 4.0 · 2.1
- Attack vector
- Network
- Complexity
- High
- Attack requirements
- Present
- Privileges needed
- Low
- User interaction
- Passive
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
Raw vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-47192.md and follow it. Check whether this project is affected by CVE-2026-47192. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/siemens/kas/commit/4cb4a3d01122ffaec9feaae768a5814092f6f9b5
- https://github.com/siemens/kas/commit/5b2114becfc154b16ef496d24f8c2191a2297f57
- https://github.com/siemens/kas/security/advisories/GHSA-4vqc-wpwg-vh7j
- https://github.com/siemens/kas/security/advisories/GHSA-qjwp-hrq6-r26r
References
- https://github.com/pypa/advisory-database/tree/main/vulns/kas/PYSEC-2026-2543.yaml
- https://github.com/siemens/kas/commit/4cb4a3d01122ffaec9feaae768a5814092f6f9b5
- https://github.com/siemens/kas/commit/5b2114becfc154b16ef496d24f8c2191a2297f57
- https://github.com/siemens/kas/security/advisories/GHSA-4vqc-wpwg-vh7j
- https://github.com/siemens/kas/security/advisories/GHSA-qjwp-hrq6-r26r