# CVE-2026-33697: CoCoS attested TLS is vulnerable to relay attacks via extracted ephemeral TLS keys > Attackers can relay attested TLS sessions to impersonate services and access data if they extract ephemeral keys via hardware or side-channel attacks. - **Severity:** High 7.5 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 26 Mar 2026 - **Updated:** 27 Mar 2026 - **Also known as:** GHSA-vfgg-mvxx-mgg7 ## What is CVE-2026-33697? CVE-2026-33697 is a high-severity vulnerability in ultravioletrs cocos, published on 26 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official 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. Weakness: CWE-346 (Origin Validation Error), CWE-322 (Key Exchange without Entity Authentication) ## Which versions are affected by CVE-2026-33697? It affects 1 product. Products: Ultraviolet Cocos Ai. ## How do I fix CVE-2026-33697? No fix has been published for CVE-2026-33697 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-33697 being exploited? There is no known exploitation of CVE-2026-33697 in the wild and no public exploit code. Public exploit code: - DugganUSA threat-intelligence contributions to the IETF Hackathon: real-world agentic-attack benchmark vectors, CVE-2026-33697 attestation analysis, MCP verification. (github_poc): https://github.com/pduggusa/dugganusa-ietf ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-33697 and fix it if it is affected. What it is: CVE-2026-33697 is a high-severity vulnerability in ultravioletrs cocos, published on 26 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-33697 in the wild and no public exploit code. Affected product: ultravioletrs cocos. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-33697/ (Markdown: https://insights.sbomify.com/CVE-2026-33697/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33697 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33697 - OSV: https://osv.dev/vulnerability/CVE-2026-33697 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-33697/ Summaries are generated and may contain mistakes; the official description above is the record.