CVE-2026-100838 in Contrast
Summary
by MITRE • 09/27/2026
Contrast is a confidential-computing runtime for Kubernetes. In versions before 1.19.1, the Kata agent policies generated by the Contrast CLI contained a flaw in the CopyFile verification that allowed arbitrary writes to the guest root filesystem. A malicious process on the untrusted host able to connect to the Kata agent VSOCK could issue a series of CopyFile requests to overwrite security-critical files in the guest or trick the workload into disclosing sensitive data, effectively amounting to a full guest takeover. Users unable to upgrade can apply an equivalent rego policy fix passed to 'contrast generate --policy'.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 09/27/2026
The vulnerability identified within Contrast, a confidential computing runtime for Kubernetes versions prior to 1.19.1, represents a critical failure in the integrity controls of the Kata Containers agent policies generated by the Contrast command-line interface. The core technical flaw resides specifically in the verification logic governing CopyFile operations executed against the guest virtual machine's root filesystem. In a secure confidential computing environment, the boundary between the untrusted host and the trusted execution environment or guest VM must be strictly enforced to prevent any unauthorized modification of system state. However, due to insufficient validation within these policies, an attacker who has gained access to the Kata agent via VSOCK sockets can exploit this weakness to bypass standard permission checks. This architectural lapse allows for arbitrary write operations directly into the root filesystem of the guest VM, effectively neutralizing the isolation guarantees that confidential computing is designed to provide.
From a threat modeling perspective, this flaw enables an attacker operating on the untrusted host to achieve full control over the guest workload. By issuing a series of carefully crafted CopyFile requests, the malicious process can overwrite security-critical configuration files, binaries, or system libraries within the guest environment. This capability goes beyond simple data exfiltration; it constitutes a complete compromise of the virtual machine's integrity. The attacker could install backdoors, modify authentication mechanisms, or alter application logic to force the workload into disclosing sensitive data that was previously protected by encryption and isolation measures. Consequently, the confidentiality and integrity properties essential for multi-tenant Kubernetes clusters running confidential workloads are entirely undermined, allowing a compromised host node to take over any guest VMs managed through this vulnerable runtime configuration.
This vulnerability aligns with CWE-284, which describes Improper Access Control, as it involves an actor bypassing intended restrictions on resource access. Furthermore, the exploitation technique maps directly to MITRE ATT&CK techniques related to Persistence and Privilege Escalation, specifically those involving file modification for establishing persistent access or altering system configurations to maintain control over a compromised host. The ability to write arbitrary files to the root filesystem is also indicative of CWE-732, which pertains to Incorrect Permission Assignment for Critical Resources, as the policy failed to restrict write permissions on sensitive paths appropriately within the guest environment.
To mitigate this risk, organizations running Contrast in production environments must prioritize upgrading to version 1.19.1 or later, where the CopyFile verification logic has been corrected to enforce strict validation of file paths and destinations. For users who are unable to upgrade immediately due to operational constraints or compatibility requirements, a temporary mitigation is available through policy regeneration. Administrators can apply an equivalent Rego policy fix by passing specific parameters to the contrast generate command with the --policy flag. This approach allows for the generation of corrected policies that restrict arbitrary writes without requiring a full runtime update, thereby restoring the necessary security boundaries until a permanent upgrade can be scheduled and deployed across the infrastructure.