Trust bypass via unbound stale attestation evidence
Published Sep 18, 2026 · Updated Sep 18, 2026
Origin validation error in Cocos AI 0.8.2 and earlier allows remote attackers to induce trust in stale attestation evidence. VerifyAttestationReportTLS leaves Policy.ReportData unset when the expected reportData is nil, empty, or omitted, so verification does not bind Evidence to the current connection. Exposure requires a relying-party integration to use acceptance from that AMD SEV-SNP path for trust, authorization, or application-data release.
Summary
What happened
Origin validation error in Cocos AI 0.8.2 and earlier allows remote attackers to induce trust in stale attestation evidence. VerifyAttestationReportTLS leaves Policy.ReportData unset when the expected reportData is nil, empty, or omitted, so verification does not bind Evidence to the current connection. Exposure requires a relying-party integration to use acceptance from that AMD SEV-SNP path for trust, authorization, or application-data release.
The record
- CVE
- CVE-2026-92702
- Published
- Sep 18, 2026
- Updated
- Sep 18, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-346
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 18, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- Intra-handshake.fail ProVerif artifactsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started