# CVE-2026-92702: Security feature bypass in cocos

> Attackers can bypass attestation checks in Cocos AI by exploiting nil reportData handling, potentially leading to unauthorized trust decisions.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-4r6g-mp48-j2rw

## What is CVE-2026-92702?

CVE-2026-92702 is a critical vulnerability in ultravioletrs cocos, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-346 (Origin Validation Error)

## Which versions are affected by CVE-2026-92702?


## How do I fix CVE-2026-92702?

No fix has been published for CVE-2026-92702 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92702 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92702 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92702 and fix it if it is affected.

What it is: CVE-2026-92702 is a critical vulnerability in ultravioletrs cocos, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92702 exists.

Affected product: ultravioletrs cocos. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92702/ (Markdown: https://insights.sbomify.com/CVE-2026-92702/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92702
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92702
- OSV: https://osv.dev/vulnerability/CVE-2026-92702

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92702/
Summaries are generated and may contain mistakes; the official description above is the record.