LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24054: Kata Containers Runtime: Host block device can be hotplugged to the VM if the container image is malformed or contains no layers

Kata Containers is an open source project focusing on a standard implementation of lightweight Virtual Machines (VMs) that perform like containers. In versions prior to 3.26.0, when a container image is malformed or contains no layers, containerd falls back to bind-mounting an empty snapshotter directory for the container rootfs. When the Kata runtime attempts to mount the container rootfs, the bind mount causes the rootfs to be detected as a block device, leading to the underlying device being hotplugged to the guest. This can cause filesystem-level errors on the host due to double inode allocation, and may lead to the host's block device being mounted as read-only. Version 3.26.0 contains a patch for the issue.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-24054 affects Kata Containers before 3.26.0. A malformed or layerless container image can cause the runtime to attach a host block device into the lightweight VM. The reported impact is host filesystem errors and possible read-only remounting, creating a serious availability and integrity risk for container platforms using Kata.

Executive priority

High priority for platform teams using Kata Containers before 3.26.0. The main business risk is host instability or data integrity impact from container image handling. Patch promptly where Kata is used, especially in multi-tenant or untrusted-image environments.

Technical view

containerd may bind-mount an empty snapshotter directory when an image is malformed or has no layers. In affected Kata Containers, that rootfs handling can misclassify the bind mount as a block device and hotplug the underlying host device into the guest. The issue is CWE-754 and is patched in Kata Containers 3.26.0.

Likely exposure

Exposure is likely limited to environments running Kata Containers versions before 3.26.0, especially where users or workloads can cause malformed or no-layer images to be processed. Standard container deployments not using Kata Containers are not identified as affected in the provided sources.

Exploitation context

The CVSS vector indicates network-reachable, low-complexity conditions with no privileges or user interaction, but the provided sources do not state active exploitation. CISA KEV status is false in the source bundle. Treat this as a credible high-severity platform risk, not confirmed in-the-wild activity.

Researcher notes

The issue centers on error handling around empty rootfs snapshots and Kata block-device detection. Public references include the GitHub advisory, the fixing commit, and relevant containerd/Kata source locations. Sources do not provide evidence of active exploitation or affected products beyond Kata Containers before 3.26.0.

Mitigation direction

  • Upgrade Kata Containers to version 3.26.0 or later.
  • Prioritize clusters accepting images from untrusted users or automated pipelines.
  • Restrict malformed or layerless images until affected runtimes are patched.
  • Review the Kata advisory and patch commit for vendor-specific deployment guidance.
  • Monitor hosts for filesystem errors or unexpected read-only remounts.

Validation and detection

  • Inventory nodes and clusters using Kata Containers as a runtime.
  • Confirm installed Kata Containers versions are 3.26.0 or later.
  • Identify workloads or pipelines that can submit malformed or no-layer images.
  • Review runtime and host logs for block hotplug or filesystem error indicators.
  • Validate the upgrade in staging before broad production rollout.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-754: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24054 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H/E:P

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H/E:P——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.8High
CVSS 4.0 vector shape for CVE-2026-24054Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
kata-containerskata-containers< 3.26.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-754 · source CWE mapping

Improper Check for Unusual or Exceptional Conditions

Improper Check for Unusual or Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.