CVE-2026-47191

What it is

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.

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.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-08-14 17:18 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-09-18 20:09 UTC Last updatedMost recent change to the record

Details

Published

2026-08-14 17:18 UTC

Last modified

2026-09-18 20:09 UTC

Exploit probability

0.2% · 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