CVE-2026-92702

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 89% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Cocos AI is a confidential computing system for running AI workloads inside trusted execution environments. In versions up to and including 0.8.2, the intra-handshake attested TLS (aTLS) AMD SEV-SNP verification path does not enforce attestation freshness when the expected reportData value is nil, empty, or omitted, leaving the SEV-SNP policy ReportData unset so the verifier accepts unrelated or stale Evidence not bound to the current connection. A relying party that uses this path without an expected reportData as a trust or authorization decision can be induced to trust an unintended attestation context; a supplied non-empty reportData is still validated. The issue is fixed in version 0.9.0.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
46(Track)
EG Risk 46/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

September 18, 2026

Last Modified

September 18, 2026

Advisory Details (4)

Auto-updated Sep 18, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github_commit, github_release, github.
github_release Patch Available

Release Notes — v0.9.0

Patch available: ultravioletrs/cocos v0.9.0

https://github.com/ultravioletrs/cocos/releases/tag/v0.9.0
github_commit Patch Available

commit 80bf813c4830 (ultravioletrs/cocos)

Patch available: ultravioletrs/cocos v0.9.0 (contains commit 80bf813c4830)

https://github.com/ultravioletrs/cocos/commit/80bf813c48300f02259b338b91f844c71be582ea
github_pr Patch Available

NOISSUE - Post-handshake aTLS

Patch available: ultravioletrs/cocos v0.9.0 (PR #582 merged 2026-03-26)

https://github.com/ultravioletrs/cocos/pull/582
github Patch Available🟡 PoC Available

Cocos AI intra-handshake attested TLS implementation can accept Evidence with nil, empty, or omitted reportData in the AMD SEV-SNP path · Advisory · ultravioletrs/cocos · GitHub

https://github.com/ultravioletrs/cocos/security/advisories/GHSA-4r6g-mp48-j2rw

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 4× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 15:59 UTCEG score recompute
  2. 2026-09-18 18:27 UTCEG score recompute
  3. 2026-09-18 17:19 UTCEG score recompute
  4. 2026-09-18 17:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92702?
CVE-2026-92702 is a critical vulnerability published on September 18, 2026. Cocos AI is a confidential computing system for running AI workloads inside trusted execution environments. In versions up to and including 0.8.2, the intra-handshake attested TLS (aTLS) AMD SEV-SNP verification path does not enforce attestation freshness when the expected reportData value is nil,…
When was CVE-2026-92702 disclosed?
CVE-2026-92702 was first published in the National Vulnerability Database on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92702 actively exploited?
CVE-2026-92702 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.1% of all scored CVEs.
What is the CVSS score of CVE-2026-92702?
CVE-2026-92702 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-92702?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92702, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-92702

Explore →

Is Your Infrastructure Affected by CVE-2026-92702?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs