CVE-2026-92702: Cocos AI: Intra-handshake attested TLS implementation can accept Evidence with nil, empty, or omitted reportData in the AMD SEV-SNP path
Cocos AI is a confidential computing system for running AI workloads inside trusted execution environments. In versions up to and including 0.8.2, the intra-handshake attested TLS (aTLS) AMD SEV-SNP verification path does not enforce attestation freshness when the expected reportData value is nil, empty, or omitted, leaving the SEV-SNP policy ReportData unset so the verifier accepts unrelated or stale Evidence not bound to the current connection. A relying party that uses this path without an expected reportData as a trust or authorization decision can be induced to trust an unintended attestation context; a supplied non-empty reportData is still validated. 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 (aTLS) AMD SEV-SNP verification pathto a version that resolves this vulnerability.Fixed in 0.9.0
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Deployments using the intra-handshake aTLS AMD SEV-SNP verification path are exposed when they use a nil, empty, or omitted expected reportData value as part of a trust or authorization decision. Configurations that supply a non-empty expected reportData continue to validate it.
What does an attacker need to exploit the issue?
An attacker needs to present unrelated or stale AMD SEV-SNP Evidence to a relying party whose verifier has no non-empty expected reportData binding for the current connection. No privileges or user interaction are required according to the provided severity vector.
What should teams do if they cannot immediately upgrade?
Ensure the relying party supplies a non-empty expected reportData value and validates it as the binding for the current connection. This avoids the affected unset ReportData condition described for nil, empty, or omitted values.
How can I determine whether my implementation is affected?
Check whether it uses Cocos AI version 0.8.2 or earlier and the intra-handshake aTLS AMD SEV-SNP verification path. It is affected if the expected reportData passed to that verification is nil, empty, or omitted; version 0.9.0 contains the fix.