---
id: "CVE-2026-119345"
kind: "vulnerability"
aliases: ["CVE-2026-119345"]
title: "Cocos AI: attestation checked once, stale trust keeps connections open"
severity: "high"
cvss: 7.2
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: []
ecosystems: []
tags: ["ai-tooling", "cocos-ai", "confidential-computing", "tls-attestation"]
not_affected_if: ["version-0.9.0-or-later"]
published_at: "2026-11-05T16:17:40+00:00"
first_seen_at: "2026-11-05T16:40:01+00:00"
updated_at: "2026-11-05T16:41:32+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-119345", "first_seen_at": "2026-11-05T16:40:01+00:00"}]
exploit_sources: []
---

# Cocos AI: attestation checked once, stale trust keeps connections open

Cocos AI, a confidential computing system for AI, verifies a workload's attestation only when an attested TLS connection is first set up. An attacker who changes the attester's code, memory state, configuration or devices after that check can keep the connection open while the peer keeps trusting the outdated evidence.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Cocos AI version and compare it with the fixed version below.
- Review whether long-lived attested TLS connections are in use between Cocos AI attesters and verifiers.

## Fix

- Cocos AI: upgrade to `0.9.0` or later.

## Timeline

- 2026-11-05T16:40:01+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-119345

## Documents

- [advisory] Vendor advisory: github.com https://github.com/ultravioletrs/cocos/security/advisories/GHSA-ghwv-vrp2-2975
- [fix] Patch: github.com https://github.com/ultravioletrs/cocos/commit/80bf813c48300f02259b338b91f844c71be582ea
- [fix] Release notes: github.com https://github.com/ultravioletrs/cocos/releases/tag/v0.9.0

## From the sources

Cocos AI is a confidential computing system for AI. Prior to 0.9.0, Cocos AI performs attestation only once when an attested TLS connection is established. An attacker who can modify the attester's workload code, memory-backed state, configuration, or attached devices after that check can keep the existing connection open while the peer continues trusting stale initial Evidence. This gap is especially significant for long-lived connections because the verifier has no mechanism to detect the changed state. This issue is fixed in version 0.9.0.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_