CVE-2026-33697 | ultravioletrs cocos up to 0.8.1 CoCoS Service key exchange without entity authentication (GHSA-vfgg-mvxx-mgg7)

VDB-353802 · CVE-2026-33697 · GHSA-VFGG-MVXX-MGG7 ULTRAVIOLETRS COCOS UP TO 0.8.1 COCOS SERVICE KEY EXCHANGE WITHOUT ENTITY AUTHENTICATION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.9 $0-$5k 3.21+ Summaryinfo A vulnerability categorized as problematic has been discovered in ultravioletrs cocos up to 0.8.1. This impacts an unknown function of the component CoCoS Service. The manipulation results in key exchange without entity authentication. This vulnerability is reported as CVE-2026-33697. The attack requires a local approach. No exploit exists. It is advisable to upgrade the affected component. Detailsinfo A vulnerability, which was classified as problematic, was found in ultravioletrs cocos up to 0.8.1. Affected is an unknown functionality of the component CoCoS Service. The manipulation with an unknown input leads to a key exchange without entity authentication vulnerability. CWE is classifying the issue as CWE-322. The product performs a key exchange with an actor without verifying the identity of that actor. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes: 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. The advisory is available at github.com. This vulnerability is traded as CVE-2026-33697 since 03/23/2026. The exploitability is told to be difficult. Local access is required to approach this attack. The technical details are unknown and an exploit is not available. Upgrading to version 0.8.2 eliminates this vulnerability. Productinfo Vendor ultravioletrs Name cocos Version 0.8.0 0.8.1 Website Product: https://github.com/ultravioletrs/cocos/ CPE 2.3info 🔒 🔒 CPE 2.2info 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 6.0 VulDB Meta Temp Score: 5.9 VulDB Base Score: 4.5 VulDB Temp Score: 4.3 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 7.5 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Key exchange without entity authentication CWE: CWE-322 / CWE-320 CAPEC: 🔒 ATT&CK: 🔒 Physical: Partially Local: Yes Remote: No Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: cocos 0.8.2 Timelineinfo 03/23/2026 CVE reserved 03/27/2026 +4 days Advisory disclosed 03/27/2026 +0 days VulDB entry created 03/27/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-vfgg-mvxx-mgg7 Status: Confirmed CVE: CVE-2026-33697 (🔒) GCVE (CVE): GCVE-0-2026-33697 GCVE (VulDB): GCVE-100-353802 Entryinfo Created: 03/27/2026 07:04 Changes: 03/27/2026 07:04 (64) Complete: 🔍 Cache ID: 99:8E7:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸