Approved changes feed: RSS · Atom

cpe:2.3:a:katacontainers:kata_containers:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorKatacontainers (ab065ca3-1681-55db-8fae-b44b1eaedf14)
ProductKata Containers (c3f6b03d-b5cf-5549-95f9-fedeee56715e)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/kata-containers/kata-containers purl2cpe 2026-06-01 10:13:44.722035
pkg:rpm/fedora/kata-containers purl2cpe 2026-06-01 10:13:44.722038

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-41326 vulnerable 2026-06-08 08:03:15.234625 Kata Containers: CopyFile Policy Subversion via Symlinks
Kata Containers is an open source project focusing on a standard implementation of lightweight Virtual Machines (VMs) that perform like containers. From v3.4.0 to v3.28.0, an oversight in the CopyFile policy (and perhaps the CopyFile handler) allows untrusted hosts to write to arbitrary locations inside the guest workload image. This can be used to overwrite binaries inside the guest and exfiltrate data from containers; even those running inside CVMs. This vulnerability is fixed in v3.29.0.
Published: 2026-04-24T18:46:21.993Z
Updated: 2026-08-24T12:07:01.406Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-24834 vulnerable 2026-06-08 07:51:18.220740 Kata Container to Guest micro VM privilege escalation
CRITICAL (9.4)
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.27.0, an issue in Kata with Cloud Hypervisor allows a user of the container to modify the file system used by the Guest micro VM ultimately achieving arbitrary code execution as root in said VM. The current understanding is this doesn’t impact the security of the Host or of other containers / VMs running on that Host (note that arm64 QEMU lacks NVDIMM read-only support: It is believed that until the upstream QEMU gains this capability, a guest write could reach the image file). Version 3.27.0 patches the issue.
Published: 2026-02-19T15:57:50.691Z
Updated: 2026-07-15T01:16:53.638Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-24054 vulnerable 2026-06-08 07:51:16.631187 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.
Published: 2026-01-29T17:16:56.418Z
Updated: 2026-01-29T21:24:54.166Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-27151 vulnerable 2026-06-08 05:23:52.152518 Details available
An issue was discovered in Kata Containers through 1.11.3 and 2.x through 2.0-rc1. The runtime will execute binaries given using annotations without any kind of validation. Someone who is granted access rights to a cluster will be able to have kata-runtime execute arbitrary binaries as root on the worker nodes.
Published: 2020-12-07T13:03:54.000Z
Updated: 2024-08-04T16:11:35.618Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.