CVE-2026-41326
Katacontainers Kata Containers vulnerability
- Published24 Apr 2026
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:NAffected products
Remediation
References
- https://access.redhat.com/errata/RHSA-2026:25200
- https://access.redhat.com/security/cve/CVE-2026-41326
- https://bugzilla.redhat.com/show_bug.cgi?id=2460859
- https://github.com/kata-containers/kata-containers/commit/1b9e49eb2763aa6ea6a99b276d3ff5e2c7f658f2
- https://github.com/kata-containers/kata-containers/security/advisories/GHSA-q49m-57vm-c8cc
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-41326.json
- http://www.openwall.com/lists/oss-security/2026/05/13/2
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-41326 being actively exploited?
CVE-2026-41326 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.37%.
How severe is CVE-2026-41326?
CVE-2026-41326 has a CVSS 3.1 base score of 8.2, rated high. EPSS estimates a 0.37% probability of exploitation.
Which products are affected by CVE-2026-41326?
Affected products include Katacontainers Confidential Containers, Katacontainers Kata Containers.
How do I fix CVE-2026-41326?
Upgrade affected software to a fixed version, for example Katacontainers Confidential Containers 0.20.0, Katacontainers Kata Containers 3.29.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-41326 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.