{
    "dataType": "CVE_RECORD",
    "dataVersion": "5.2",
    "cveMetadata": {
        "cveId": "CVE-2026-47191",
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "state": "PUBLISHED",
        "assignerShortName": "GitHub_M",
        "dateReserved": "2026-05-18T22:07:37.435Z",
        "datePublished": "2026-08-14T16:35:48.128Z",
        "dateUpdated": "2026-08-14T16:35:48.128Z"
    },
    "containers": {
        "cna": {
            "title": "kas checks out SHA-like git branches as valid commits",
            "problemTypes": [
                {
                    "descriptions": [
                        {
                            "cweId": "CWE-347",
                            "lang": "en",
                            "description": "CWE-347: Improper Verification of Cryptographic Signature",
                            "type": "CWE"
                        }
                    ]
                }
            ],
            "metrics": [
                {
                    "cvssV4_0": {
                        "attackVector": "NETWORK",
                        "attackComplexity": "HIGH",
                        "attackRequirements": "PRESENT",
                        "privilegesRequired": "LOW",
                        "userInteraction": "PASSIVE",
                        "vulnConfidentialityImpact": "LOW",
                        "vulnIntegrityImpact": "LOW",
                        "vulnAvailabilityImpact": "LOW",
                        "subConfidentialityImpact": "NONE",
                        "subIntegrityImpact": "NONE",
                        "subAvailabilityImpact": "NONE",
                        "baseScore": 2.1,
                        "baseSeverity": "LOW",
                        "vectorString": "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",
                        "version": "4.0"
                    }
                }
            ],
            "references": [
                {
                    "name": "https://github.com/siemens/kas/security/advisories/GHSA-qjwp-hrq6-r26r",
                    "tags": [
                        "x_refsource_CONFIRM"
                    ],
                    "url": "https://github.com/siemens/kas/security/advisories/GHSA-qjwp-hrq6-r26r"
                },
                {
                    "name": "https://github.com/siemens/kas/commit/4cb4a3d01122ffaec9feaae768a5814092f6f9b5",
                    "tags": [
                        "x_refsource_MISC"
                    ],
                    "url": "https://github.com/siemens/kas/commit/4cb4a3d01122ffaec9feaae768a5814092f6f9b5"
                },
                {
                    "name": "https://github.com/pypa/advisory-database/tree/main/vulns/kas/PYSEC-2026-2544.yaml",
                    "tags": [
                        "x_refsource_MISC"
                    ],
                    "url": "https://github.com/pypa/advisory-database/tree/main/vulns/kas/PYSEC-2026-2544.yaml"
                }
            ],
            "affected": [
                {
                    "vendor": "siemens",
                    "product": "kas",
                    "versions": [
                        {
                            "version": "< 5.3",
                            "status": "affected"
                        }
                    ]
                }
            ],
            "providerMetadata": {
                "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
                "shortName": "GitHub_M",
                "dateUpdated": "2026-08-14T16:35:48.128Z"
            },
            "descriptions": [
                {
                    "lang": "en",
                    "value": "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."
                }
            ],
            "source": {
                "advisory": "GHSA-qjwp-hrq6-r26r",
                "discovery": "UNKNOWN"
            }
        }
    }
}