Description
Contrast, Edgeless Systems' runtime for confidential containers on Kubernetes, is affected in versions up to and including 1.9.0. The VOLUME directive in a Dockerfile (config.volumes in the OCI image configuration) is only a hint and is not handled specially by Kubernetes, but containerd adds a mount point for it when Kubernetes sets none, requiring the runtime to be able to push arbitrary data to the Kata agent. As a result, on bare-metal Contrast deployments (AKS deployments are not affected) that run an image declaring at least one VOLUME for which no Kubernetes mount exists at that path, the untrusted host can write arbitrary file trees below that mount point inside the confidential container, compromising the integrity of a directory that is typically important to the application's core functionality. Version 1.9.1 fixes the issue by disallowing this configuration in `contrast generate`.
Published: 2026-09-27
Score: 5.1 Medium
EPSS: n/a
KEV: No
Impact: Integrity compromise via arbitrary file writes inside confidential containers
Action: Immediate Patch
AI Analysis

Impact

Contrast is a runtime for confidential containers on Kubernetes. In versions up to 1.9.0, handling of the Docker VOLUME directive is incomplete: the directive is treated only as metadata, but containerd mounts the specified path regardless of a Kubernetes volume. The runtime must send data to the Kata agent to populate this mount, and because the VOLUME can point to an arbitrary directory, an untrusted host can write arbitrary data beneath that mount point inside the confidential container. This compromises the integrity of directories that are critical to the application, even though the container remains isolated from the host. The weakness is a CWE‑693: Improper Authorization.

Affected Systems

The affected product is Edgeless Systems Contrast, versions 1.9.0 and earlier. The vulnerability manifests when a container image declares at least one VOLUME and the Kubernetes configuration does not bind a corresponding host volume. It does not affect AKS deployments because AKS implements an alternative volume handling for Contrast. Version 1.9.1 through the release notes disables the problematic configuration during generation.

Risk and Exploitability

The CVSS score of 5.1 places the vulnerability in the medium impact range. EPSS data is not available, and the issue is not listed in the CISA KEV catalog, suggesting limited public exploitation. Likely exploitation requires the attacker to have host or cluster‑level access to deploy or modify a container image that declares a VOLUME, or to run Impacted Contrast on bare‑metal nodes. Once executed, the attacker can overwrite files inside the confidential container, potentially altering application behavior or installing malicious components.

Generated by OpenCVE AI on September 27, 2026 at 03:30 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Contrast to version 1.9.1 or later, which disallows VOLUME configurations that lack a Kubernetes mount.
  • Validate that any Docker images used with Contrast do not declare VOLUME directives that are not bound to a real Kubernetes volume.
  • Restrict host access to nodes running Contrast; employ role‑based access controls so that only trusted users can modify container images or deploy new containers.

Generated by OpenCVE AI on September 27, 2026 at 03:30 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 27 Sep 2026 02:00:00 +0000

Type Values Removed Values Added
Description Contrast, Edgeless Systems' runtime for confidential containers on Kubernetes, is affected in versions up to and including 1.9.0. The VOLUME directive in a Dockerfile (config.volumes in the OCI image configuration) is only a hint and is not handled specially by Kubernetes, but containerd adds a mount point for it when Kubernetes sets none, requiring the runtime to be able to push arbitrary data to the Kata agent. As a result, on bare-metal Contrast deployments (AKS deployments are not affected) that run an image declaring at least one VOLUME for which no Kubernetes mount exists at that path, the untrusted host can write arbitrary file trees below that mount point inside the confidential container, compromising the integrity of a directory that is typically important to the application's core functionality. Version 1.9.1 fixes the issue by disallowing this configuration in `contrast generate`.
Title Edgeless Systems Contrast before 1.9.1 Insecure Volume Mount
Weaknesses CWE-693
References
Metrics cvssV3_1

{'score': 3.5, 'vector': 'CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N'}

cvssV4_0

{'score': 5.1, 'vector': 'CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-09-27T01:28:26.587Z

Reserved: 2026-09-27T00:18:22.540Z

Link: CVE-2025-71424

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-27T02:17:16.393

Modified: 2026-09-27T02:17:16.393

Link: CVE-2025-71424

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-27T03:45:18Z

Weaknesses
  • CWE-693

    Protection Mechanism Failure