CVE-2026-112377
Received Received - Intake

Attestation TLS Relay Vulnerability in CCC Attestation SIG

Vulnerability report for CVE-2026-112377, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-19

Last updated on: 2026-10-19

Assigner: VulnCheck

Description

CCC Attestation SIG attested-tls-poc through commit 731ca82 fails to bind early attestation Evidence to the TLS connection, allowing attackers to relay valid Evidence from a genuine attester. Attackers holding an extracted attested TLS private key can forward the relying party's nonce to a genuine attester and replay its Evidence to impersonate the attested workload and intercept data.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-19
Last Modified
2026-10-19
Generated
2026-10-19
AI Q&A
2026-10-19
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
CCC-Attestation attested-tls-poc 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-346 The product does not properly verify that the source of data or communication is valid.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-112377 is a vulnerability in CCC Attestation SIG's attested-tls-poc implementation where early attestation evidence is not properly bound to the TLS connection. This allows attackers to relay valid attestation data from a genuine device to impersonate a workload. Attackers with a stolen attested TLS private key can forward a relying party's nonce to a real attester and replay its evidence, intercepting data by masquerading as the attested workload.

Detection Guidance

The vulnerability is specific to the CCC Attestation SIG attested-tls-poc implementation up to commit 731ca82. To detect it, check if your system uses this version or earlier. Inspect logs for relayed attestation evidence or unexpected nonce forwarding during TLS handshakes. Formal analysis tools like ProVerif can verify the binding mechanism, but this requires expertise.

Impact Analysis

This vulnerability enables attackers to impersonate attested workloads, intercept sensitive data, or bypass authentication. If you use systems relying on attested-tls-poc up to commit 731ca82, your communications could be compromised. Attackers may gain unauthorized access to encrypted data or perform man-in-the-middle attacks, undermining trust in the attested TLS mechanism.

Compliance Impact

This vulnerability could lead to unauthorized data access or interception, violating GDPR's data protection principles and HIPAA's security requirements for protected health information. Non-compliance may result in legal penalties, reputational damage, and loss of trust. Organizations using vulnerable implementations must address this flaw to maintain regulatory compliance.

Mitigation Strategies

Immediately stop using the attested-tls-poc implementation up to commit 731ca82. Update to a patched version if available or migrate to alternative solutions like the IETF's SEAT Working Group recommendations. Monitor for unusual TLS handshake patterns or relayed attestation data.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-112377. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart