Skip to main content
VulnerabilityPublished

CVE-2025-71424: Contrast, Edgeless Systems' runtime for confidential containers on Kubernetes, is affected in

Affects contrastSource GCVE Database

0
Compare
Authoritative record:CVE-2025-71424· Medium 5.1

Not known to be exploited · CVSS 5.1 Medium : upgrade to 1.9.1 when convenient.

Data as of 11 Nov 2026, 23:24 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.9.1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.

What to do

Upgrade edgelesssys/contrast to 1.9.1.

Affected software

ProductAffectedFixed in
GitHubedgelesssys/contrastpkg:github/edgelesssys/contrastOther threatsAffected
  • <1.9.1
Fixed in
  • 1.9.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Version 1.9.1 of Contrast fixes this vulnerability by disallowing the problematic VOLUME configuration in the 'contrast generate' command. Users should upgrade to version 1.9.1 or later to remediate this issue. Since this is not a cloud service, remediation depends on applying this update. No additional mitigations are indicated.

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`.

References

Community reviews

Loading reviews…