CVE-2026-92701: Cocos AI: Intra-handshake attested TLS implementation is vulnerable to session-misbinding attacks for Intel TDX verifier path
trusted execution environments. In versions up to and including 0.8.2, the intra-handshake attested TLS (aTLS) Intel TDX verification path does not copy the expected current-session freshness value into the TDX quote-body policy before quote validation, so structurally valid TDX QuoteV4 Evidence is accepted without checking that its REPORTDATA field matches the reportData expected for the current session. A relying party using this path can therefore accept Evidence with a mismatched or reused reportData and release application data after the handshake, enabling session-misbinding to an unintended attestation context. The issue is fixed in version 0.9.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Cocos AI (intra-handshake attested TLS for Intel TDX verifier path)to a version that resolves this vulnerability.Fixed in 0.9.0
Event History
Frequently Asked Questions
Which deployments are exposed?
Deployments using the Cocos AI intra-handshake aTLS Intel TDX verification path are affected if they run version 0.8.2 or earlier. The issue is specific to the Intel TDX verifier path described; the provided information does not establish impact on other attestation paths.
What must an attacker provide to exploit this issue?
An attacker needs to provide structurally valid TDX QuoteV4 Evidence whose REPORT_DATA does not match the reportData expected for the current session. Because the freshness value is not incorporated into quote-body policy validation, reused or mismatched reportData can be accepted.
What is the practical security impact?
A relying party can release application data after the handshake while accepting Evidence bound to an unintended attestation context. This enables session-misbinding attacks.
How can I remediate the issue?
Upgrade to Cocos AI version 0.9.0, which fixes the issue. The supplied information does not describe a workaround for affected versions.