Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.2amended

Cocos AI Intra-handshake attested TLS implementation is vulnerable to TOCTOU Attacks

CVE-2026-119345GHSA-ghwv-vrp2-2975

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/ultravioletrs/cocos 0.9.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.2 · 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 · score source
EPSS
  • CVE-2026-119345: 0.12% estimated exploitation activity in the next 30 days; percentile 1.67 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary An attacker who can modify the attested workload’s code, memory-backed state, or configuration after the initial attestation — but without necessarily terminating the existing TLS connection — can cause the peer to continue trusting the connection as if the originally attested state were still running.

Details Once attestation is successfully appraised and connection is established, there is a window of vulnerability from the establishment of connection to the termination of connection where an attacker can modify the state of the workload and platform at runtime on the TLS endpoint acting as the Attester. Workload state includes code, data, and configuration. Other examples of state changes at the workload level include cases where a new device (such as a GPU) is connected, or where a connected device is disconnected, since the connection establishment. In Cocos AI, there is no mechanism for the peer to know that some state has changed in the Attester after the…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-ghwv-vrp2-2975

  2. Revision 1 · created ·

    Published from ghsa record GHSA-ghwv-vrp2-2975

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-119345

Advisory: Cocos AI Intra-handshake attested TLS implementation is vulnerable to TOCTOU Attacks
IDs: CVE-2026-119345, GHSA-ghwv-vrp2-2975
Record: https://patchnext.com/advisories/cve-2026-119345 (revision 2, source checked 11 Nov 2026, 07:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/ultravioletrs/cocos 0.9.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/ultravioletrs/cocos: affected < 0.9.0; fixed in 0.9.0

## Suggested inspection (read-only)
- Go github.com/ultravioletrs/cocos: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/ultravioletrs/cocos.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-ghwv-vrp2-2975 (GitHub-reviewed advisory GHSA-ghwv-vrp2-2975 lists affected ranges: Go github.com/ultravioletrs/cocos >=0 <=0.8.2)
- Verified: https://osv.dev/vulnerability/GHSA-ghwv-vrp2-2975 (OSV record GHSA-ghwv-vrp2-2975 lists affected ranges: Go github.com/ultravioletrs/cocos >=0 <0.9.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…