CVE-2026-33697
High · 7.5CVSS
7.5
EPSS
0.1%
Published
Mar 27, 2026
CISA due date
—
The record
Cocos AI is a confidential computing system for AI. The current implementation of attested TLS (aTLS) in CoCoS is vulnerable to a relay attack affecting all versions from v0.4.0 through v0.8.2. This vulnerability is present in both the AMD SEV-SNP and Intel TDX deployment targets supported by CoCoS. In the affected design, an attacker may be able to extract the ephemeral TLS private key used during the intra-handshake attestation. Because the attestation evidence is bound to the ephemeral key but not to the TLS channel, possession of that key is sufficient to relay or divert the attested TLS session. A client will accept the connection under false assumptions about the endpoint it is communicating with — the attestation report cannot distinguish the genuine attested service from the attacker's relay. This undermines the intended authentication guarantees of attested TLS. A successful attack may allow an attacker to impersonate an attested CoCoS service and access data or operations that the client intended to send only to the genuine attested endpoint. Exploitation requires the attacker to first extract the ephemeral TLS private key, which is possible through physical access to the server hardware, transient execution attacks, or side-channel attacks. Note that the aTLS implementation was fully redesigned in v0.7.0, but the redesign does not address this vulnerability. The relay attack weakness is architectural and affects all releases in the v0.4.0–v0.8.2 range. This vulnerability class was formally analyzed and demonstrated across multiple attested TLS implementations, including CoCoS, by researchers whose findings were disclosed to the IETF TLS Working Group. Formal verification was conducted using ProVerif. As of time of publication, there is no patch available. No complete workaround is available. The following hardening measures reduce but do not eliminate the risk: Keep TEE firmware and microcode up to date to reduce the key-extraction surface; define strict attestation policies that validate all available report fields, including firmware versions, TCB levels, and platform configuration registers; and/or enable mutual aTLS with CA-signed certificates where deployment architecture permits.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|
Related vulnerabilities
- CVE-2026-94423 Net::LibSSH versions before 0.004 for Perl authenticate to an unverified server because… CWE-322
- CVE-2026-94140 Rex versions through 1.16.1 for Perl accept an unknown SSH host key for remote rsync… CWE-322
- CVE-2026-107675 FFmpeg through 9.0.2 contains a missing host key verification vulnerability in the… CWE-322
- CVE-2026-18654 Key exchange without entity authentication in the EMR SSH helper commands in Amazon AWS… CWE-322
- CVE-2026-11745 A vulnerability has been identified in centraldogma-server-mirror-git versions prior to… CWE-322
- CVE-2026-45361 Apache Airflow providers-google's `ComputeEngineSSHHook` disables SSH host-key… CWE-322
- GHSA-mxg3-432p-mr72 goshs: SSH host key verification disabled, allowing transparent MITM of every tunnelled… CWE-322
- CVE-2026-44467 The Claude Desktop app gives you Claude Code with a graphical interface built for running… CWE-322