Skip to main content
VulnerabilityPublished

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

Affects ultravioletrs cocosSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical · fixed in 0.9.0 : patch ultravioletrs cocos as a priority.

Data as of 5 Nov 2026, 16:20 UTC

CVSS 4.0 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.09.1
Patch
Available – fixed in 0.9.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 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 5 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
ultravioletrscocosAffected
  • <=0.8.2
Fixed in–

AI-suggested

This vulnerability is addressed in Cocos AI version 0.9.0. Users should upgrade to version 0.9.0 or later to mitigate this issue. However, because the vulnerability arises from the confidential computing threat model itself, it cannot be fully mitigated by source code changes alone. Additional architectural or operational controls may be necessary to manage risk.

Description

CVE-2026-119344 is a critical origin validation error in the Cocos AI confidential computing system versions 0.8.2 and earlier. The vulnerability allows a remote attacker controlling another trusted platform to substitute valid attestation Evidence, causing authorization of an incorrect platform. This flaw arises because the system accepts attestation Evidence without binding it to a unique platform owner or enforcing revocation. The issue is addressed in version 0.9.0, but cannot be fully mitigated by source code changes alone due to the underlying confidential computing threat model.

References

Community reviews

Loading reviews…