Skip to main content
VulnerabilityPublished

CVE-2026-119345: github.com/ultravioletrs/cocos · Cocos AI Intra-handshake attested TLS implementation is vulnerable to TOCTOU Attacks

Affects github.com/ultravioletrs/cocosSource GCVE Database

0
Compare
Authoritative record:CVE-2026-119345· High 7.2

Not known to be exploited · CVSS 7.2 High : upgrade to 0.9.0 soon.

Data as of 10 Nov 2026, 17:48 UTC

CVSS 4.0 base score
7.2High
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.07.2
Patch
Available – fixed in 0.9.0
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/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 10 Nov 2026.

What to do

Upgrade github.com/ultravioletrs/cocos to 0.9.0.

Affected software

ProductAffectedFixed in
Gogithub.com/ultravioletrs/cocosAffected
  • <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

A patch is available in Cocos AI version 0.9.0 that addresses this vulnerability. Users should upgrade to version 0.9.0 or later. The vendor recommends implementing post-handshake re-attestation at periodic or user-defined intervals to ensure the freshness of attestation evidence during long-lived connections.

Description

Cocos AI's intra-handshake attested TLS implementation is vulnerable to a Time-Of-Check to Time-Of-Use (TOCTOU) attack. An attacker who can modify the attested workload's code, memory state, or configuration after the initial attestation but without terminating the TLS connection can cause the peer to continue trusting a stale attestation state. This vulnerability affects long-lived TLS connections because attestation is only performed once at connection establishment, with no mechanism for re-attestation during the connection lifetime. The issue was discovered through formal analysis and affects versions prior to 0.9.0.

References

Community reviews

Loading reviews…