Description
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.
Published: 2026-03-26
Score: 7.5 High
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized access via TLS session relay
Action: Apply mitigations
AI Analysis

Impact

Attested TLS in the CoCoS system permits an attacker to extract the temporary private key used during the TLS handshake. This is a cryptographic key‑compromise weakness (CWE‑322) and also involves an unchecked transfer of credentials (CWE‑346). With the key, an attacker can relay or divert an attested TLS session, making a client accept a connection to a false endpoint while the attestation report cannot differentiate the genuine attested service. The result is a breach of the authentication guarantees of attested TLS, allowing the attacker to impersonate a CoCoS service and obtain or tamper with data intended for the legitimate endpoint.

Affected Systems

The vulnerability affects ultravioletrs CoCoS versions from v0.4.0 through v0.8.2 on both AMD SEV‑SNP and Intel TDX deployment targets.

Risk and Exploitability

The CVSS score of 7.5 indicates high severity, but the EPSS score of less than 1% suggests a low probability of exploitation. The vulnerability is not listed in the CISA KEV catalog. Exploitation requires the attacker to retrieve the temporary TLS key, which can be achieved through physical access to the server hardware, transient‑execution attacks, or side‑channel attacks. The likely attack vector is therefore either compromised physical security or advanced side‑channel techniques. No patch is currently available.

Generated by OpenCVE AI on April 10, 2026 at 16:54 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Keep TEE firmware and microcode up to date to reduce the key‑extraction surface.
  • Enforce strict attestation policies that validate all report fields, including firmware versions, TCB levels, and platform configuration registers.
  • If deployment architecture permits, enable mutual attested TLS with CA‑signed certificates to bind the TLS channel to a trusted endpoint.
  • Ensure physical security of servers to prevent hardware‑based key extraction and side‑channel exploitation.

Generated by OpenCVE AI on April 10, 2026 at 16:54 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 10 Apr 2026 15:45:00 +0000

Type Values Removed Values Added
First Time appeared Ultraviolet
Ultraviolet cocos Ai
CPEs cpe:2.3:a:ultraviolet:cocos_ai:*:*:*:*:*:go:*:*
Vendors & Products Ultraviolet
Ultraviolet cocos Ai

Fri, 27 Mar 2026 20:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Fri, 27 Mar 2026 08:45:00 +0000

Type Values Removed Values Added
First Time appeared Ultravioletrs
Ultravioletrs cocos
Vendors & Products Ultravioletrs
Ultravioletrs cocos

Fri, 27 Mar 2026 04:00:00 +0000

Type Values Removed Values Added
Description 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.
Title CoCoS attested TLS is vulnerable to relay attacks via extracted ephemeral TLS keys
Weaknesses CWE-322
CWE-346
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N'}


Subscriptions

Ultraviolet Cocos Ai
Ultravioletrs Cocos
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-03-27T19:59:52.799Z

Reserved: 2026-03-23T17:06:05.745Z

Link: CVE-2026-33697

cve-icon Vulnrichment

Updated: 2026-03-27T13:27:45.286Z

cve-icon NVD

Status : Analyzed

Published: 2026-03-27T00:16:23.133

Modified: 2026-04-10T15:38:46.883

Link: CVE-2026-33697

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-04-13T14:28:17Z

Weaknesses