CVE-2026-119345 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
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.
first public Sep 25, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running Cocos AI attesters and verifiers for confidential AI workloads, especially where TLS connections stay open for a long time. The sources do not say which deployment configurations are exposed beyond versions before 0.9.0.
Not affected if version-0.9.0-or-later
Who cares cocos-ai, confidential-computing, tls-attestation
0.9.0 or later.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.
This page as .md ·
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.