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.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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)

Note that Nessus relies on the presence of the package as reported by the vendor.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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)

ID	Name	Product	Family	Type	Severity
318342	Linux Distros Unpatched Vulnerability : CVE-2026-47191	Nessus	Misc.	Local	low
442562	SCA: security update for kas (GHSA-qjwp-hrq6-r26r)	Tenable Cloud Security	SCA Checks	Local	low
442562	SCA: security update for kas (GHSA-qjwp-hrq6-r26r)	Tenable Self-Hosted Container Security	SCA Checks	Local	low

Detections

Analytics

CVE-2026-47191

low

Tenable Plugins

low

low

low