CVE-2026-119345

Cocos AI can keep trusting stale attestation during a live connection

Ultraviolet · Cocos AI attested TLS

First documented disclosure · Review checkpoint

Summary

The peer may continue trusting a workload whose state changed after its initial attestation.

Severity and exploitation evidence

High · 7.2/10 · CVSS 4.0. Severity source.

Exploitation not established: The finding was demonstrated through formal analysis. Production exploitation is not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The old implementation checks the workload once at connection establishment and does not notify the peer of later state changes.

Conditions required

The attacker can alter workload code, state, configuration or attached devices while keeping an established connection alive.

Potential impact

A long-lived trusted session can outlast the evidence that justified it.

Affected versions and configurations

Before 0.9.0, according to the CNA.

Fix and mitigation status

The CNA identifies 0.9.0. The maintainer recommends post-handshake re-attestation at periodic or policy-defined intervals.

Practical next steps

Upgrade and verify that the deployed policy actually requests fresh attestation during long sessions and handles failed revalidation.

Operating lesson

Trust decisions need a freshness policy for the full lifetime of a connection.

Evidence and limits

The March 20 PR introduces post-handshake attestation as a feature without describing this stale-state finding. September 25 is the reviewed Cocos-specific vulnerability disclosure; the CVE followed November 5. A new transport alone does not prove a periodic appraisal policy is active.

Sources