Contrast
Contrast before 1.16.0 Remote Attestation Relay Attack
Contrast before 1.16.0 is susceptible to remote attestation relay attacks. Contrast accepted any TEE attestation report that verified correctly and contained the expected firmware patch levels and software measurements, regardless of which machine produced it, so attestation was not bound to specific, physically trusted hardware. An attacker who can both intercept network traffic between the CLI and the Coordinator (or between the Coordinator and an attested component) and forge reports or extract secrets from any single TEE machine under their physical control can relay such a report to impersonate a Contrast Coordinator or a Contrast workload, defeating identity verification in Contrast's attested TLS (aTLS).
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.16.0
Fixed in 1.16.0
Mitigation
Upgrade contrast to 1.16.0 or later.
References
- Vendor advisory github.com/edgelesssys/contrast/security/advis…
Timeline
Days relative to CVE publicationFirst public PoC 9 h after publication; not in CISA KEV. First PoC: murrez/CVE-2026-100835 (created 27 Sep 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| murrez/CVE-2026-100835 | 27 Sep 2026 +9 h | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.