← Back
CVE-2026-47243
Path Traversal in github.com/kata-containers/kata-containers (CVE-2026-47243)
Summary
path traversal in github.com/kata-containers/kata-containers (CVE-2026-47243). Risk of unauthorized operations or information disclosure. Exploitable via ``virtiofsd``. Mitigation: upgrade to `0.0.0-20260519062212-ffa59ce3aa78` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-47243** has been found in github.com/kata-containers/kata-containers.
Attackers can target a specific entry point like ``virtiofsd`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade github.com/kata-containers/kata-containers to **0.0.0-20260519062212-ffa59ce3aa78** or later.
If unsure, ask your IT team or search "github.com/kata-containers/kata-containers CVE-2026-47243" on the vendor's site.
CVE-2026-47243 (github.com/kata-containers/kata-containers) — CWE-22 /
Attack surface: `virtiofsd` / `FUSE_SYMLINK` / `main` / `shared_fs`
Patched: `0.0.0-20260519062212-ffa59ce3aa78` — apply immediately
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
**Path traversal** (CWE-22) exists in github.com/kata-containers/kata-containers. Attackers reach the vulnerable code path via ``virtiofsd`` without authentication.
📍 Affected scope
github.com/kata-containers/kata-containers — . Attack surface: `virtiofsd` / `FUSE_SYMLINK` / `main` / `shared_fs`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.0.0-20260519062212-ffa59ce3aa78**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/kata-containers/kata-containers' .` 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 'github.com/kata-containers/kata-containers' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/kata-containers/kata-containers` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/kata-containers/kata-containers to 0.0.0-20260519062212-ffa59ce3aa78ステージング環境で 0.0.0-20260519062212-ffa59ce3aa78 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/kata-containers/kata-containers
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.0.0-20260519062212-ffa59ce3aa78"}]}]
References
- package https://github.com/kata-containers/kata-containers
- web https://github.com/kata-containers/kata-containers/security/advisories/GHSA-2gv2-cffp-j227
- web https://github.com/kata-containers/kata-containers/commit/ffa59ce3aa7877d067c9a372df0c329a23a01744
- web https://github.com/kata-containers/kata-containers/releases/tag/3.31.0
- web https://github.com/advisories/GHSA-2gv2-cffp-j227
- web af854a3a-2127-422b-91ae-364da2661108