VulnerabilityPublished 18 Sep 2026Updated 13 Oct 2026

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

Affects ultravioletrs cocosSource CVE Database V5

Compare

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

Data as of 2 Nov 2026, 22: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 17% 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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade cocos and ultravioletrs/cocos to 0.9.0.

Affected software

Product	Affected	Fixed in
ultravioletrscocos	Affected <0.9.0	Fixed in 0.9.0
GitHubultravioletrs/cocos`pkg:github/ultravioletrs/cocos`Other threats	Affected <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

Upgrade to Cocos AI version 0.9.0 or later, where the vulnerable verification path has been removed and replaced with a more secure post-handshake attestation mechanism. No other mitigation is indicated by the vendor advisory.

Description

CVE-2026-92702 is a critical origin validation error in Cocos AI versions before 0.9.0. The vulnerability involves improper handling of attestation report data in the AMD SEV-SNP verifier, allowing a relying party to accept attestation evidence unrelated to the current session when empty expected report data is provided. This can lead to incorrect trust, authorization, or data release decisions. The issue was fixed in version 0.9.0 by removing the affected verification path during migration to post-handshake attestation.

Impact

An attacker could exploit this vulnerability by causing a relying party to accept attestation evidence that does not correspond to the current session, potentially leading to unauthorized trust, authorization, or release of application data. The CVSS 3.1 score of 9.1 reflects high confidentiality and integrity impact with no required privileges or user interaction.

Summary

In Cocos AI 0.8.2 and earlier, the VerifyAttestationReportTLS function in the AMD SEV-SNP verifier sets Policy.ReportData only if the caller provides non-empty expected reportData. If a relying party passes nil or empty expected reportData, the verifier may accept SEV-SNP evidence unrelated to the current connection, potentially causing trust or authorization decisions to be made based on an unintended attestation context. This origin validation error (CWE-346) was addressed in Cocos AI 0.9.0 by removing the vulnerable verifier path as part of a migration to post-handshake attestation.

CWE-346Origin Validation Error (opens in a new tab)
Class weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not properly verify that the source of data or communication is valid.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V14.5.2 (opens in a new tab)
V14.5.3 (opens in a new tab)
V1.4.4 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cache Poisoning (opens in a new tab)
DNS Cache Poisoning (opens in a new tab)
Exploit Script-Based APIs (opens in a new tab)
Application API Message Manipulation via Man-in-the-Middle (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Oct 2026, 20:10 UTC

WeaknessesCWE-346

Technical details

References

Community reviews

Related threats