← Back
CVE-2026-47192
Vulnerability in kas (CVE-2026-47192)
Summary
vulnerability in kas (CVE-2026-47192). Risk of unauthorized operations or information disclosure. Exploitable via ``_source_dir``. Mitigation: upgrade to `5.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-47192** has been found in kas.
Attackers can target a specific entry point like ``_source_dir`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade kas to **5.3** or later.
If unsure, ask your IT team or search "kas CVE-2026-47192" on the vendor's site.
CVE-2026-47192 (kas) — CWE-347 /
Attack surface: `_source_dir`
Patched: `5.3` — apply immediately
Workaround: Pin the expected signature key via its fingerprint, also when storing it as file in a repository.
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. Attackers reach the vulnerable code path via ``_source_dir`` without authentication.
📍 Affected scope
kas — . Attack surface: `_source_dir`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.3**.
🛡️ Workaround
Workaround: Pin the expected signature key via its fingerprint, also when storing it as file in a repository.
🔍 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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'kas' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `kas` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Pin the expected signature key via its fingerprint, also when storing it as file in a repository.パッチが適用されるまでの応急処置として、Pin the expected signature key via its fingerprint, also when storing it as file in a repository. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade kas to 5.3ステージング環境で 5.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
kas
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3"}]}]
PyPI
kas
[{"type":"ECOSYSTEM","events":[{"introduced":"4.8"},{"fixed":"5.3"}]}]