kas checks out SHA-like git branches as valid commits (CVE-2026-47191) | HOL Guard CVE

Low · CVSS 2.1CVE-2026-47191GHSA-QJWP-HRQ6-R26R

kas checks out SHA-like git branches as valid commits

Answer in brief

CVE-2026-47191 records a Low severity (CVSS 2.1) vulnerability in kas checks out SHA-like git branches as valid commits. The current sources do not mark it as known exploited. The current feed maps siemens/kas (generic), kas (pip), kas (pypi). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 14, 2026Updated Aug 18, 2026Source checked Sep 17, 2026First seen by HOL Jun 11, 2026Material review Aug 18, 2026

Upstream Advisory

Key facts

Risk: Low · CVSS 2.1
Exploitation: Not marked as known exploited
Affected software: 3 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 2.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps siemens/kas (generic), kas (pip), kas (pypi). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
siemens/kasgeneric	< 5.3	Not reported
kaspip	<5.3	5.3
kaspypi	>=0 <5.3	5.3

Recommended response

Check inventory. Check lockfiles and deployed manifests for siemens/kas, kas, kas.
Review the reported fix. Update kas to 5.3; kas to 5.3 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 14, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 18, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Jun 11, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.