LiveActive security incident?Get immediate response
CVE Record

CVE-2026-41326: 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.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A malicious or compromised host can abuse Kata Containers file-copy handling to write anywhere inside a guest workload. This could overwrite guest binaries or expose container data, including data in confidential VMs. Kata Containers versions 3.4.0 through 3.28.x are affected; version 3.29.0 fixes the issue.

Executive priority

Treat this as a high-priority isolation failure. Expedite remediation for affected multi-tenant, sensitive-data, and confidential-computing environments. Although active exploitation is not established, potential guest compromise and data exposure justify prompt version verification and upgrading.

Technical view

Symlink handling can subvert the CopyFile policy, enabling an untrusted host to redirect writes to arbitrary guest paths. The CVSS 3.1 score is 8.8, with low attack complexity and high confidentiality, integrity, and availability impact across a changed scope. The advisory indicates possible CopyFile handler involvement but does not confirm it.

Likely exposure

Exposure exists where Kata Containers versions 3.4.0 through 3.28.x are deployed and the host-to-guest boundary is expected to protect workloads. Risk is especially important for confidential-VM deployments because the flaw can undermine guest isolation from an untrusted or compromised host.

Exploitation context

The supplied record is not listed in KEV, and the source bundle provides no evidence of active exploitation. A public advisory and corrective commit exist, which may increase researcher and attacker awareness, but their availability does not establish exploitation in the wild.

Researcher notes

The record maps the issue to CWE-1220 and CWE-61 and assigns CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. Confirm affected runtime versions and examine the upstream advisory and corrective commit for implementation details. Evidence provided does not establish active exploitation or a supported workaround beyond upgrading.

Mitigation direction

  • Upgrade Kata Containers to version 3.29.0 or later.
  • Apply the applicable Red Hat security update when using Red Hat-packaged components.
  • If upgrading is delayed, consult vendor guidance for supported temporary risk-reduction measures.
  • Prioritize environments relying on protection from untrusted hosts, particularly confidential-VM workloads.

Validation and detection

  • Inventory all Kata Containers versions and flag releases from 3.4.0 through 3.28.x.
  • Confirm updated deployments report Kata Containers version 3.29.0 or later.
  • Identify workloads where untrusted or compromised hosts could access CopyFile functionality.
  • Review affected guests for unexplained binary changes or suspicious access to container data.
Prepared
Confidence
high
Sources
5

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-1220: 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
cwe · low confidence lookup

CWE-61: 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
cve · low confidence lookup

CVE-2026-41326 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 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

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.

2CVSS vectors
5Timeline events
3ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

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 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H26redhat-SADP
8.2CVSS 4.0HighCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:H/SI:N/SA:N——GitHub_M

Vulnerability scoring details

Base CVSS 4.0 score

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

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

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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Reported to Red Hat.

  3. ADP timelineredhat-SADP

    Made public.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
redhat-SADPkata-containers: Arbitrary file write inside guest image via CopyFile policy
other:Red Hat severity ratingcvssV3_1
  • 2026-04-22T19:00:36.343Z: Reported to Red Hat.
  • 2026-04-22T19:01:25.112Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
kata-containerskata-containers>= 3.4.0, < 3.29.0Listed
Weakness

CWE details

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

CWE-1220 · source CWE mapping

Insufficient Granularity of Access Control

Insufficient Granularity of Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-61 · source CWE mapping

UNIX Symbolic Link (Symlink) Following

UNIX Symbolic Link (Symlink) Following represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.