← Back
CVE-2026-24834
critical
CVSS 9.3
Vulnerability in github.com/kata-containers/kata-containers/src/runtime (CVE-2026-24834)
Summary
vulnerability in github.com/kata-containers/kata-containers/src/runtime (CVE-2026-24834). Successful exploitation can lead to full system takeover. Exploitable via ``ND_REGION_PAGEMAP``. Mitigation: upgrade to `0.0.0-20260219090056-6a672503973b` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-24834** has been found in github.com/kata-containers/kata-containers/src/runtime.
Attackers can target a specific entry point like ``ND_REGION_PAGEMAP`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.3/10.
What to do: upgrade github.com/kata-containers/kata-containers/src/runtime to **0.0.0-20260219090056-6a672503973b** or later.
If unsure, ask your IT team or search "github.com/kata-containers/kata-containers/src/runtime CVE-2026-24834" on the vendor's site.
CVE-2026-24834 (github.com/kata-containers/kata-containers/src/runtime) — CWE-281 / CVSS v3 9.3
Attack vector: local / unauthenticated / no user interaction
Attack surface: `ND_REGION_PAGEMAP` / `ND_REGION_ASYNC` / `virtio_pmem` / `MAP_PRIVATE`
Patched: `0.0.0-20260219090056-6a672503973b` — 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
**A vulnerability** (CWE-281) exists in github.com/kata-containers/kata-containers/src/runtime. Attackers reach the vulnerable code path via ``ND_REGION_PAGEMAP`` without authentication.
📍 Affected scope
github.com/kata-containers/kata-containers/src/runtime — . Attack surface: `ND_REGION_PAGEMAP` / `ND_REGION_ASYNC` / `virtio_pmem` / `MAP_PRIVATE`.
🔥 Severity
Severity: Critical (CVSS 9.3/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **0.0.0-20260219090056-6a672503973b**.
🛡️ 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/src/runtime' .` 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/src/runtime' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/kata-containers/kata-containers/src/runtime` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/kata-containers/kata-containers/src/runtime to 0.0.0-20260219090056-6a672503973bステージング環境で 0.0.0-20260219090056-6a672503973b に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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/src/runtime
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.0-20260219090056-6a672503973b"}]}]
References
- web https://github.com/kata-containers/kata-containers/commit/6a672503973bf7c687053e459bfff8a9652e16bf
- web https://github.com/kata-containers/kata-containers/releases/tag/3.27.0
- web https://github.com/kata-containers/kata-containers/security/advisories/GHSA-wwj6-vghv-5p64
- web https://access.redhat.com/security/cve/CVE-2026-24834
- web https://bugzilla.redhat.com/show_bug.cgi?id=2441025
- web https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-24834.json
- web https://nvd.nist.gov/vuln/detail/CVE-2026-24834
- web https://github.com/advisories/GHSA-wwj6-vghv-5p64