Is CVE-2026-41326 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-41326 being exploited in the wild.

How severe is CVE-2026-41326?

High severity, with a CVSS score of 8.2, published 24 April 2026.

Which products and versions are affected?

Confidential Containers Project Confidential Containers v0.9.0 - v0.19.0; github.com/kata-containers/kata-containers (Go) < 0.0.0-20260422180503-1b9e49eb2763, SEMVER:introduced=0,fixed=0.0.0-20260422180503-1b9e49eb2763; Kata Containers Containers < 0.0.0-20260422180503-1b9e49eb2763; Kata Containers Project Kata Containers v3.4.0 - v3.28.0.

Is there a fix for CVE-2026-41326?

Yes. github.com/kata-containers/kata-containers (Go): upgrade to 0.0.0-20260422180503-1b9e49eb2763 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-41326 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-41326?

Check whether you run Confidential Containers Project Confidential Containers, github.com/kata-containers/kata-containers (Go), Kata Containers Containers or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-41326: Kata Containers arbitrary file write via CopyFile symlink subversion

Q: Is there a fix for CVE-2026-41326?

Yes. github.com/kata-containers/kata-containers (Go): upgrade to 0.0.0-20260422180503-1b9e49eb2763 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-41326 attacked?

It is attacked with local access, in a software library.

Q: Am I affected by CVE-2026-41326?

Check whether you run Confidential Containers Project Confidential Containers, github.com/kata-containers/kata-containers (Go), Kata Containers Containers or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-41326 · Severity: high · CVSS 8.2 · Published 2026-04-24

Kata Containers, a tool used to run secure and lightweight virtual machines, contains a security flaw in how it handles file copying between the host system and the virtual machine. An attacker with access to the host system could bypass security policies to write malicious files or overwrite critical system binaries inside the protected virtual machine. This could lead to the theft of sensitive data or full control over the applications running within the secure environment, even when using hardware-based confidential computing.

Technologies: github.com/kata-containers/kata-containers (Go). Vendors: Go.

Quick answers

Is CVE-2026-41326 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-41326 being exploited in the wild.
How severe is CVE-2026-41326?: High severity, with a CVSS score of 8.2, published 24 April 2026.
Which products and versions are affected?: Confidential Containers Project Confidential Containers v0.9.0 - v0.19.0; github.com/kata-containers/kata-containers (Go) < 0.0.0-20260422180503-1b9e49eb2763, SEMVER:introduced=0,fixed=0.0.0-20260422180503-1b9e49eb2763; Kata Containers Containers < 0.0.0-20260422180503-1b9e49eb2763; Kata Containers Project Kata Containers v3.4.0 - v3.28.0.
Is there a fix for CVE-2026-41326?: Yes. github.com/kata-containers/kata-containers (Go): upgrade to 0.0.0-20260422180503-1b9e49eb2763 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41326 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-41326?: Check whether you run Confidential Containers Project Confidential Containers, github.com/kata-containers/kata-containers (Go), Kata Containers Containers or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/kata-containers/kata-containers (Go): upgrade to 0.0.0-20260422180503-1b9e49eb2763 or later
```
go get github.com/kata-containers/kata-containers@v0.0.0-20260422180503-1b9e49eb2763
```

Technical details

A vulnerability exists in the Kata Containers 'CopyFile' API due to insufficient validation of symbolic links within the 'genpolicy' implementation. While the security policy checks that the destination path is within a designated shared directory, it fails to account for the fact that the Kata Agent supports creating symlinks via the same API. An attacker on the host can create a symlink in the shared directory that points to a sensitive location (such as a system binary) within the guest image, and then use a subsequent CopyFile request to overwrite that target. This allows for arbitrary code execution in the guest and data exfiltration, bypassing the protections intended for Confidential Virtual Machines (CVMs). The issue is fixed in Kata Containers v3.29.0 and Confidential Containers v0.20.0.

Affected products

Kata Containers Kata Containers v3.4.0 - v3.28.0
Kata Containers Confidential Containers v0.9.0 - v0.19.0
Red Hat Red Hat OpenShift Container Platform 4.19, 4

Identifiers

CVE-2026-41326
GHSA-q49m-57vm-c8cc
GO-2026-5563

Timeline

2026-04-22: advisory: GitHub Security Advisory published
2026-04-22: patched: Fix committed to repository
2026-04-24: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.