Answer in brief
CVE-2025-71426 records a High severity (CVSS 7.1) vulnerability in Contrast before 1.4.1 Coordinator Impersonation via Unauthenticated Recovery. The current sources do not mark it as known exploited. The current feed maps edgelesssys/contrast (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps edgelesssys/contrast (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| edgelesssys/contrastgeneric | >=0 <1.4.1 | 1.4.1 |
Published upstream
Sep 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 27, 2026
Contrast is a confidential-computing runtime for Kubernetes. In versions before 1.4.1, a recovering Coordinator does not verify the seed supplied by the recovering party. An attacker can therefore stand up a rogue Coordinator whose manifest passes validation but whose secret seed is attacker-controlled. If network traffic is redirected from the legitimate Coordinator to the attacker's Coordinator, a workload owner can be impersonated when they either set a new manifest without comparing the returned root CA certificate against the existing one (the default behavior of the contrast CLI) or verify the Coordinator without comparing the root CA certificate against a trusted reference. Under these 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 are not affected.
Quoted source text, attributed separately from HOL analysis.