CVE-2026-119344 · Other
NO FIX YET · SEE WHAT TO DO
Cocos AI, a confidential computing system, accepts trusted execution environment attestation evidence without binding it to a specific platform owner or machine identity, and does not enforce revocation. An attacker who controls another platform trusted by the same verifier can substitute that platform's valid evidence and get the wrong platform authorized.
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 as an attestation verifier for confidential computing workloads at version 0.8.2 or earlier. The exposure depends on whether other platforms trusted by the same verifier could be controlled or compromised by an attacker. Deployments not using Cocos AI for attestation are not affected.
Not affected if not-using-cocos-ai, version-0.9.0-or-later
Who cares attestation, cocos-ai, confidential-computing, tee
0.8.2 and earlier are affected.0.9.0, which the description says addresses this issue.Cocos AI is a confidential computing system for AI. In version 0.8.2 and earlier, Cocos AI accepts trusted execution environment attestation Evidence when firmware patch levels and software measurements match, without binding the Evidence to an allowed platform owner or unique machine identity and without enforcing revocation. A remote attacker who controls or compromises another platform trusted by the same verifier can substitute valid Evidence from that platform and cause authorization of the wrong platform. This vulnerability is addressed in 0.9.0. However, this vulnerability can't be patched in source code alone, since the vulnerability arises from the confidential computing threat model itself.
This page as .md · .json · CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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.