DEBIAN-CVE-2026-47191
- Source
- https://security-tracker.debian.org/tracker/CVE-2026-47191
- Import Source
- https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-47191.json
- JSON Data
- https://api.osv.dev/v1/vulns/DEBIAN-CVE-2026-47191
- Upstream
- Published
- 2026-08-14T17:18:15Z
- Modified
- 2026-09-19T22:47:42Z
- Severity
-
- 2.1 (Low) CVSS_V4 - 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 CVSS Calculator
- Summary
- [none]
- Details
-
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.
- References
Affected packages
Debian:12 / kas
Package
- Name
- kas
- Purl
- pkg:deb/debian/kas?arch=source&distro=bookworm
Affected ranges
- Type
- ECOSYSTEM
- Events
-
Introduced0 Unknown introduced version / All previous versions are affected
Debian:13 / kas
Package
- Name
- kas
- Purl
- pkg:deb/debian/kas?arch=source&distro=trixie
Debian:14 / kas
Package
- Name
- kas
- Purl
- pkg:deb/debian/kas?arch=source&distro=forky