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.
CVE-2026-47191
This low-severity CVE scores 2.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 95% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 2.1
- EG Score
- 2.1(medium)
- EG Risk
- 10(Track)EG Risk 10/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity21% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 5%
- KEV
- Not listed
Published
June 1, 2026
Last Modified
August 18, 2026
References (3)
- security-advisories@githubhttps://github.com/pypa/advisory-database/tree/main/vulns/kas/PYSEC-2026-2544.yaml
- security-advisories@githubhttps://github.com/siemens/kas/commit/4cb4a3d01122ffaec9feaae768a5814092f6f9b5
- security-advisories@githubhttps://github.com/siemens/kas/security/advisories/GHSA-qjwp-hrq6-r26r
Vendor Advisories for CVE-2026-47191(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(5 across 5 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| kas | 2.3.3-2 ... 5.3-1 (26 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| kas | 3.1-2 ... 5.3-1 (18 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| kas | 4.8.1-2 ... 5.3-1 (6 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| kas | 4.8.1-2, 4.8.2-1, 5.0-1, 5.1-1, 5.2-1 | 5.3-1 | — |
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| kas | 0.11.0 ... 5.2 (51 versions) | 5.3 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 16× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 03:57 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 07:42 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 02:21 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-14 17:44 UTCEG score recompute
- 2026-08-14 16:44 UTCEG score recompute▲ 2.10
- 2026-08-14 16:44 UTCMITRE cvelistV5CVSS v3 → 2.1 · CVSS v4 → 2.1
- 2026-07-31 05:44 UTCEG score recompute
- 2026-07-26 23:43 UTCEG score recompute
- 2026-07-23 03:17 UTCEG score recompute
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-01 14:49 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-347
Frequently asked(5)
What is CVE-2026-47191?
When was CVE-2026-47191 disclosed?
Is CVE-2026-47191 actively exploited?
What is the CVSS score of CVE-2026-47191?
How do I remediate CVE-2026-47191?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47191
Is Your Infrastructure Affected by CVE-2026-47191?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.