Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-109359 Overview
CVE-2026-109359 is an improper verification vulnerability [CWE-345] in Edgeless Systems Contrast, a confidential computing runtime for Kubernetes. The flaw affects Contrast versions 1.8.0 through versions before 1.24.1. The Coordinator peer recovery process fails to confirm that the serving peer uses the same manifest generation as the requester. Attackers with write access to manifest history can replay a superseded history head. This replay allows withdrawn workloads to obtain trusted mesh certificates. If the secret seed is also exposed, attackers can disclose the Mesh Certificate Authority (CA) key.
Critical Impact
Attackers can issue trusted mesh certificates to withdrawn workloads or expose the Mesh CA private key, compromising confidentiality and integrity across the service mesh.
Affected Products
- Edgeless Systems Contrast 1.8.0 through versions before 1.24.1
- Contrast Coordinator peer recovery component
- Workloads relying on Contrast Mesh CA-issued certificates
Discovery Timeline
- 2026-10-12 - CVE-2026-109359 published to NVD
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-109359
Vulnerability Analysis
Contrast relies on a Coordinator service that attests workloads and issues certificates signed by a Mesh CA. The Coordinator tracks a manifest history that defines which workloads are authorized. During peer recovery, one Coordinator instance synchronizes trust state from a peer. The vulnerability stems from the recovery routine not validating that the serving peer operates on the same manifest generation as the requesting peer. This gap allows a stale or superseded history head to be presented as authoritative. Workloads removed from the current manifest can therefore re-enter the trust domain with valid mesh certificates. When combined with knowledge of the secret seed, an attacker can derive and extract the Mesh CA key.
Root Cause
The root cause is insufficient verification of authenticity and freshness in the peer recovery handshake [CWE-345]. The Coordinator accepts a manifest history head from a peer without binding the exchange to the current manifest generation. The protocol lacks a check that ties recovery responses to the requester's view of the latest manifest state.
Attack Vector
Exploitation requires network access to the Coordinator and high privileges, specifically write access to manifest history storage. An attacker with these capabilities replays a superseded history head during a recovery request. The Coordinator then treats withdrawn workloads as valid and issues mesh certificates to them. If the attacker additionally holds the secret seed, the Mesh CA private key becomes recoverable, breaking trust guarantees across the service mesh.
See the GitHub Security Advisory GHSA-rxcv-p3px-m3c3 and the VulnCheck Advisory on Mesh CA Key Exposure for the vendor-provided technical details.
Detection Methods for CVE-2026-109359
Indicators of Compromise
- Mesh certificates issued to workload identities that were previously withdrawn from the active manifest.
- Coordinator peer recovery operations that reference manifest generations older than the current head.
- Unexpected writes or rollbacks observed in manifest history storage.
- Mesh CA signing activity originating from unknown or unattested nodes.
Detection Strategies
- Correlate Coordinator audit logs with manifest history versioning to detect generation mismatches during recovery.
- Alert on any peer recovery exchange where the responder's manifest generation lags the requester's by more than one revision.
- Compare the set of certificate-holding workloads against the current authorized workload set in each manifest generation.
Monitoring Recommendations
- Monitor access to the secret seed material and alert on any read operation outside provisioned recovery flows.
- Track Coordinator-to-Coordinator traffic and flag connections from peers presenting stale manifest heads.
- Record all Mesh CA signing events and reconcile them against workload attestation records daily.
How to Mitigate CVE-2026-109359
Immediate Actions Required
- Upgrade Contrast to version 1.24.1 or later on all Coordinator instances.
- Rotate the Mesh CA key and the secret seed if any possibility of exposure exists.
- Audit manifest history storage access controls and remove unnecessary write permissions.
- Re-attest all workloads currently holding mesh certificates and revoke those not present in the current manifest.
Patch Information
Edgeless Systems addressed CVE-2026-109359 in Contrast 1.24.1. The fix ensures that peer recovery validates the serving peer's manifest generation against the requester's, preventing superseded history heads from being accepted. Refer to the GitHub Security Advisory GHSA-rxcv-p3px-m3c3 for upgrade guidance.
Workarounds
- Restrict write access to manifest history storage to a minimal set of trusted administrators.
- Protect the secret seed with strict access controls and hardware-backed secret storage where available.
- Disable or restrict Coordinator peer recovery operations until the upgrade to 1.24.1 is complete.
- Monitor and manually review certificate issuance events to the Mesh CA until patched.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

