CVE-2026-24834

9.3 CRITICAL

📋 TL;DR

This vulnerability in Kata Containers allows a container user to modify the Guest micro VM's file system, leading to arbitrary code execution as root within that VM. It affects Kata Containers versions prior to 3.27.0. The vulnerability does not compromise the host system or other containers/VMs on the same host.

💻 Affected Systems

Products:
  • Kata Containers
Versions: All versions prior to 3.27.0
Operating Systems: Linux
Default Config Vulnerable: ⚠️ Yes
Notes: Arm64 QEMU lacks NVDIMM read-only support, potentially allowing guest writes to reach the image file.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

An attacker with container access achieves root-level code execution within the Guest micro VM, potentially compromising the container's integrity and data.

🟠

Likely Case

Container users gain elevated privileges within their own VM environment, allowing them to bypass container security controls and execute unauthorized code.

🟢

If Mitigated

With proper isolation and monitoring, the impact is limited to the affected VM without host compromise.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Exploitation requires container user access and knowledge of the vulnerability.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 3.27.0

Vendor Advisory: https://github.com/kata-containers/kata-containers/security/advisories/GHSA-wwj6-vghv-5p64

Restart Required: Yes

Instructions:

1. Update Kata Containers to version 3.27.0 or later. 2. Restart all containers using Kata runtime. 3. Verify the update was successful.

🔧 Temporary Workarounds

Disable Kata Containers

linux

Temporarily switch to alternative container runtimes like runc until patched.

Configure container runtime to use runc instead of kata-runtime

🧯 If You Can't Patch

  • Isolate affected containers in separate network segments.
  • Implement strict access controls and monitoring for container activities.

🔍 How to Verify

Check if Vulnerable:

Check Kata Containers version: kata-runtime --version

Check Version:

kata-runtime --version

Verify Fix Applied:

Confirm version is 3.27.0 or later: kata-runtime --version | grep -E '3\.27\.[0-9]+|^[4-9]\.[0-9]+'

📡 Detection & Monitoring

Log Indicators:

  • Unexpected file system modifications in Guest VM logs
  • Unauthorized privilege escalation attempts within containers

Network Indicators:

  • Unusual outbound connections from containers

SIEM Query:

source="kata-containers" AND (event="file_modification" OR event="privilege_escalation")

🔗 References

📤 Share & Export