Cocos AI Intra-handshake attested TLS implementation is vulnerable to TOCTOU Attacks
Cocos AI versions v0.8.2 and earlier attest the workload only when a connection is set up, not for the rest of the connection. Fixed in 0.9.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.9.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected versions are v0.8.2 and earlier (fixed in 0.9.0). Attestation is performed only once at connection establishment and not re-checked for the life of the connection.
- Published
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 12/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Cocos AI, a confidential computing system for AI, versions before 0.9.0 check attestation only once when an attested TLS connection is set up, so an attacker with low-privilege local access can change the attester's workload code, memory state, configuration, or attached devices afterward and keep the existing connection open while the peer still trusts the outdated initial evidence. The attacker can therefore undermine the integrity of attested connections, which matters most for long-lived ones.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.2/10CVSS 7.2
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected versions are v0.8.2 and earlier (fixed in 0.9.0). Attestation is performed only once at connection establishment and not re-checked for the life of the connection.Upgrade to a fixed version: 0.9.0.
Workaround: Allow re-attestation of the workload after periodic or user-defined intervals using post-handshake attestation.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- ultravioletrs cocos
fixed in 0.9.0
Evidence 4
- Advisory
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-119345
Is CVE-2026-119345 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Cocos AI checks the workload's attestation once, when the connection is established, and does not check it again for the life of the connection. A workload that changes after that first check is not re-verified.Source: github.com
Which versions are affected by CVE-2026-119345?
cocos: before 0.9.0.Source: cve.now feed data
Am I affected, and how do I check?
Cocos AI v0.8.2 and earlier are affected. To check a deployment, look at the installed Cocos AI version.Source: github.com
How do I fix CVE-2026-119345?
Upgrade Cocos AI to 0.9.0 or later, which is the fixed version listed for this issue.Source: github.com