Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-47191

Vulnerability in kas (CVE-2026-47191)

Summary

Vulnerability in kas (CVE-2026-47191). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.3 or later.

Original description

The description as published by the source.

Impact

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.

Patches

Commit https://github.com/siemens/kas/commit/4cb4a3d01122ffaec9feaae768a5814092f6f9b5 is resolving this issue. It has been released along with kas version 5.3.

Workarounds

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.

Credits

That such issues exist was already reported 3 years ago by Aditya Sirish A Yelgundhalli. At this point, no strong integrity checks for external repositories were in place in kas, and Siemens stated in the kas documentation that such attacks are considered out of scope. This hasn't changed for SHA-1 commits as explained above. If a repo provides SHA-256 commits, though, those may be considered strong enough (even if not providing authentic…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-47191 has been found in kas.
Risk of unauthorized operations or information disclosure.
What to do: upgrade kas to 5.3 or later.
If unsure, ask your IT team or search "kas CVE-2026-47191" on the vendor's site.

CVE-2026-47191 (kas) — CWE-347
Patched: 5.3 — apply immediately
Workaround: Avoid relying solely on the commit ID for integrity validation of a repository that might become under control of a malicious 3rd party.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-347) exists in kas.

📍 Affected scope

Check the vendor advisory for the affected versions of kas.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 5.3.

🛡️ Workaround

Workaround: Avoid relying solely on the commit ID for integrity validation of a repository that might become under control of a malicious 3rd party.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'kas' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'kas' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で kas を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Avoid relying solely on the commit ID for integrity validation of a repository that might become under control of a malicious 3rd party.

    パッチが適用されるまでの応急処置として、Avoid relying solely on the commit ID for integrity validation of a repository that might become under control of a malicious 3rd party. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade kas to 5.3

    ステージング環境で 5.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip kas
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3"}]}]
PyPI kas
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details