{"answers":{"affected":"3 open source packages ship an affected version, including kas.","exploited":"There is no known exploitation of CVE-2026-47191 in the wild and no public exploit code.","fix":"Upgrade kas to 5.3 or later.","what":"CVE-2026-47191 is a low-severity vulnerability in siemens kas, published on 14 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-47191 and fix it if it is affected.\n\nWhat it is: CVE-2026-47191 is a low-severity vulnerability in siemens kas, published on 14 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-47191 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- kas (PyPI): affected all versions; fixed in 5.3\n- kas (PyPI): affected all versions; fixed in 5.3\n- kas (PyPI): affected all versions; fixed in 5.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-47191/ (Markdown: https://insights.sbomify.com/CVE-2026-47191/index.md)","id":"CVE-2026-47191","markdown":"https://insights.sbomify.com/CVE-2026-47191/index.md","name":"CVE-2026-47191","record":{"aliases":["DEBIAN-CVE-2026-47191","GHSA-qjwp-hrq6-r26r","PYSEC-2026-2544","UBUNTU-CVE-2026-47191"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Bitbake setup tool","requires_auth":"low_privilege","summary":"Attackers can trick kas into checking out malicious branches instead of validated commits, enabling supply chain attacks on Bitbake projects.","user_interaction":"required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.1,"severity":"low","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"kas is a setup tool for bitbake based projects. Prior to version 5.3, when relying solely on a git commit ID (SHA-1 or SHA-256) to qualify if a checkout of a repository is equivalent to the state validated while adding its commit ID to a kas configuration, users may be tricked to check out a branch of the same name from this repository. This implies that the referenced repository has been taken over by an attacker and modified to carry such a branch. SHA-1 commits may also be replaced by creating hash collisions, so the primary impact of this issue is on SHA-256 commit IDs. Version 5.3 fixes the issue. As a workaround, avoid relying solely on the commit ID for integrity validation of a repository that might become under control of a malicious 3rd party. If available, additional validate cryptographically signed commits or tags. Alternatively, mirror the repository to a save place, validate its integrity, and use this instead of the original one.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"kas checks out SHA-like git branches as valid commits","id":"CVE-2026-47191","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"supply_chain","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"kas's late signature validation may allow unnoticed repository manipulations","id":"CVE-2026-47192"},"packages":[{"ecosystem":"PyPI","fixed":["5.3"],"introduced":["0"],"last_affected":[],"package":"kas","purl":null,"source":"GHSA-qjwp-hrq6-r26r"},{"ecosystem":"PyPI","fixed":["5.3"],"introduced":["0"],"last_affected":[],"package":"kas","purl":"pkg:pypi/kas","source":"GHSA-qjwp-hrq6-r26r"},{"ecosystem":"PyPI","fixed":["5.3"],"introduced":["0"],"last_affected":[],"package":"kas","purl":"pkg:pypi/kas","source":"PYSEC-2026-2544"}],"prev":{"headline":"IPAM controller service account granted unnecessary full access to Secrets","id":"CVE-2026-47190"},"products":["kas"],"published":"2026-08-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-18","vendors":["siemens"]},"summary":"Attackers can trick kas into checking out malicious branches instead of validated commits, enabling supply chain attacks on Bitbake projects.","url":"https://insights.sbomify.com/CVE-2026-47191/"}