Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-41326: Kata Containers is an open source project focusing on a standard implementation of lightweight Virtual Machine

41
This month
HIGH 8.2REMOTEUPGRADEUPGRADE

CVE-2026-41326 is a high-severity flaw (CVSS 8.2) affecting confidential containers, kata containers. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score8.2 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.3% (top 72%)
CISA exploited listNo
WeaknessCWE-61, CWE-1220
Published2026-04-24
Last modified2026-08-24
Publisher (CNA): GitHub, Inc. · Vendor: katacontainers

Share: LinkedIn · X · Reddit

Last updated 2026-08-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

katacontainers confidential containers UPGRADE
Affected: >= 0.9.0 and < 0.20.0
Fixed in: 0.20.0
Safe to downgrade to: a release before 0.9.0
1. Check installed version
apt-cache policy confidential-containers || rpm -q confidential-containers || confidential-containers --version
2. UPGRADE to 0.20.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade confidential-containers
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade confidential-containers
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 0.9.0 (Debian / Ubuntu)
apt-cache madison confidential-containers sudo apt install confidential-containers=<VERSION_BEFORE_0.9.0> sudo apt-mark hold confidential-containers
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list confidential-containers sudo dnf downgrade confidential-containers-<VERSION_BEFORE_0.9.0> sudo dnf versionlock add confidential-containers
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
katacontainers kata containers UPGRADE
Affected: >= 3.4.0 and < 3.29.0
Fixed in: 3.29.0
Safe to downgrade to: a release before 3.4.0
1. Check installed version
apt-cache policy kata-containers || rpm -q kata-containers || kata-containers --version
2. UPGRADE to 3.29.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade kata-containers
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade kata-containers
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.4.0 (Debian / Ubuntu)
apt-cache madison kata-containers sudo apt install kata-containers=<VERSION_BEFORE_3.4.0> sudo apt-mark hold kata-containers
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list kata-containers sudo dnf downgrade kata-containers-<VERSION_BEFORE_3.4.0> sudo dnf versionlock add kata-containers
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-41326?

confidential containers: upgrade to 0.20.0; kata containers: upgrade to 3.29.0. Exact commands for each OS are on this page.

Is CVE-2026-41326 being exploited?

CVE-2026-41326 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-41326 affect?

CVE-2026-41326 affects confidential containers, kata containers. Severity is high (CVSS 8.2). 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 handle

How urgent is CVE-2026-41326?

Priority 41/100. High severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.