Cocos AI is a confidential computing system for AI. In Cocos AI 0.8.2 and earlier, VerifyAttestationReportTLS in the AMD SEV-SNP verifier sets Policy.ReportData only when its caller supplies non-empty expected reportData. A relying-party integration that passes nil or empty expected reportData while relying on that value for current-session freshness can therefore accept SEV-SNP evidence unrelated to the current connection and make a trust, authorization, or application-data release decision for an unintended attestation context. This issue was fixed in Cocos AI 0.9.0 by removing the affected verifier path as part of the migration to post-handshake attestation.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 9.1NVD modified 2026-10-13 21:19
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://github.com/ultravioletrs/cocos/commit/80bf813c48300f02259b338b91f844c71be582ea
- https://github.com/ultravioletrs/cocos/pull/582
- https://github.com/ultravioletrs/cocos/releases/tag/v0.9.0
- https://github.com/ultravioletrs/cocos/security/advisories/GHSA-4r6g-mp48-j2rw
- https://github.com/ultravioletrs/cocos/security/advisories/GHSA-4r6g-mp48-j2rw