Skip to main content
VulnerabilityPublished Updated

CVE-2026-92701: ultravioletrs cocos · Origin Validation Error

Affects ultravioletrs cocosSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical : upgrade to 0.9.0 as a priority.

Data as of 2 Nov 2026, 10:58 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.9.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

Upgrade cocos and ultravioletrs/cocos to 0.9.0.

Affected software

ProductAffectedFixed in
ultravioletrscocosAffected
  • <0.9.0
Fixed in
  • 0.9.0
GitHubultravioletrs/cocospkg:github/ultravioletrs/cocosOther threatsAffected
  • <0.9.0
Fixed in
  • 0.9.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in Cocos AI version 0.9.0 by removing the affected verifier path during migration to post-handshake attestation. Users should upgrade to version 0.9.0 or later to remediate this issue. No other mitigations are indicated.

Description

CVE-2026-92701 is a critical origin validation vulnerability in Cocos AI versions 0.8.2 and earlier. The Intel TDX aTLS verifier's VerifTeeAttestation function fails to apply the expected current-session value to TdQuoteBodyPolicy.ReportData before validating TDX QuoteV4 evidence. This allows acceptance of structurally valid but mismatched or reused REPORT_DATA, potentially causing trust or authorization decisions to be made for unrelated attestation contexts. The issue was fixed in version 0.9.0 by removing the affected verifier path during migration to post-handshake attestation.

References

Community reviews

Loading reviews…