Contrast is an open‑source confidential‑computing runtime for Kubernetes. Versions prior to 1.4.1 do not verify the seed supplied during Coordinator recovery. An attacker can therefore launch a rogue Coordinator whose manifest is accepted as valid, but whose secret seed is attacker‑controlled. If traffic is redirected from the legitimate Coordinator to the attacker’s Coordinator, a workload owner can be impersonated when the workload owner either sets a new manifest without checking the returned root CA certificate against the existing one (the default contrast CLI behavior) or verifies the Coordinator without comparing the root CA certificate against a trusted reference. Under those conditions the attacker can issue certificates that chain back to the rogue Coordinator’s root CA and recover arbitrary workload secrets of workloads deployed after the attack. Secrets of the legitimate Coordinator (seed, workload secrets, CA), workload integrity, and certificates chaining to the mesh CA remain unaffected.

The affected vendor is Edgeless Systems, product Contrast, as distributed on the Kubernetes platform. The vulnerability applies to all Contrast releases before version 1.4.1. No specific patch version numbers are listed beyond this, so the advisory recommends upgrading to 1.4.1 or newer to mitigate the problem.

The CVSS score of 7.1 indicates a high severity environment. The EPSS score is not available, so the current exploitation likelihood cannot be quantified. The vulnerability is not listed in the CISA KEV catalog. Potential attackers must control or redirect network traffic to the Coordinator and exploit the coordinator recovery mechanism; therefore threat production requires some network access or administrative capabilities. The attack path allows attackers to impersonate workload owners and recover workload secrets, which could lead to confidentiality breaches and unauthorized credential use.