Skip to content
CVE-2026-112377: TLS Relay Vulnerability Disclosed

CVE-2026-112377: TLS Relay Vulnerability Disclosed

First seen 19 Oct 2026, 19:51 UTC • •
API

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 19, 2026 at 20:51 UTC
  • •CVE-2026-112377 allows attackers to impersonate trusted workloads.
  • •The vulnerability is critical with a CVSS score of 9.1.
  • •Mitigation includes restricting access and applying a handshake-binding fix.

CVE-2026-112377 was published on October 19, 2026, detailing a flaw in CCC Attestation SIG's attested-tls-poc. The vulnerability allows attackers to relay valid attestation Evidence from a genuine attester by exploiting a failure to bind early attestation Evidence to the TLS connection. Attackers with an extracted attested TLS private key can impersonate the attested workload and intercept sensitive data. The risk is deemed high-impact but conditional, as the urgency of the threat remains unconfirmed due to the lack of KEV, SSVC, EPSS, and PoC status. Teams using remote-attestation-based TLS in test environments are particularly vulnerable. Mitigation steps include restricting access to attestation services and applying the maintainer's handshake-binding fix. The CVSS score is 9.1, indicating a severity level.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-10-19
CVE-2026-112377 published
CVE-2026-112377 disclosed a critical vulnerability in CCC Attestation SIG's attested-tls-poc.
Redpacketsecurity
2026-10-19
CVE-2026-112377 CVSS score assigned
The vulnerability received a CVSS score of 9.1, indicating critical severity.
Sploitus

More articles in this cluster (2)

Following this threat?

Track CVE-2026-112377 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Extracted Entities (2)

1 / 2

Common questions

What systems are affected by CVE-2026-112377?
The vulnerability affects systems using CCC Attestation SIG's attested-tls-poc, particularly in remote-attestation-based TLS setups.
What is the recommended mitigation?
Restrict access to attestation services and apply the maintainer's handshake-binding fix.
Is there confirmed exploitation of this vulnerability?
Currently, there is no confirmed exploitation reported, but proof-of-concept code is available.