Early Attestation is Very Harmful. Why is it Required?

Transport Layer Security (TLS) is a widely used protocol for secure channel establishment. However, it lacks an inherent mechanism for validating the security state of the workload and its platform. To address this, remote attestation can be integrated into TLS, which is named attested TLS protocol.

There are two key approaches for this integration, namely early (intra-handshake) and standard (post-handshake) attestation. We also present insights from formal verification using the state-of-the-art symbolic security analysis tool ProVerif that led to the discovery of the critical- and high-severity CVEs in early attestation. In particular, we share our discovered critical-severity CVEs, such as CVE-2026-92701, CVE-2026-92702, CVE-2026-100835, each of CVSS 9.1, and other critical- and high-severity security concerns against early attestation

The attendees will gain technical insights into the latest developments of standardization of attested TLS protocols in the IETF, and will be able to provide feedback on the standardization effort of attested TLS.

Our thorough formal security analysis shows that early attestation is potentially vulnerable to replay, relay, diversion, and misbinding attacks. Our analysis shows that:

1. Early attestation adds unnecessary complexity in the handshake.
2. Early attestation results in several security and privacy problems, such as those captured in published CVEs.
3. All use cases of early attestation can be handled with standard attestation while offering better security properties.

Because of critical-severity CVEs and fundamental architecture problems in early attestation, we believe early attestation is very harmful to the TEE attestation ecosystem. We would like to discuss with the community whether it is necessary.