ATTESTED-TLS-POC · CVE-2026-129092 · Other
NO FIX YET · SEE WHAT TO DO
The attested-tls-poc proof-of-concept appraises a machine's attestation Evidence only once during the TLS handshake and never again afterward. A local attacker on the attesting endpoint can change workload code, data, configuration or attached devices such as GPUs while peers keep trusting the original Evidence.
first public Nov 13, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Anyone running the attested-tls-poc proof-of-concept (commits up to 731ca82) to trust a workload via TLS attestation. An attacker needs local, privileged access to the attesting machine to change code, data, config or GPUs after the handshake while peers still trust the original Evidence. Teams not using this archived research code can skip it.
Not affected if not-using-attested-tls-poc
Who cares archived, attested-tls-poc, confidential-computing, tls-attestation
Check whether your code or build depends on or vendors CCC-Attestation/attested-tls-poc (any commit up to 731ca82ed533fc7a1092be980887ae2e34261da2, i.e. all of it, since the last commit was Oct 2023): search repos, submodules and Dockerfiles for that repository URL.
CCC Attestation SIG attested-tls-poc through commit 731ca82 contains a time-of-check time-of-use vulnerability because Evidence is appraised only once during the TLS handshake, without post-handshake re-attestation. Attackers with local access to the attesting endpoint can alter workload code, data, configuration, or attached devices like GPUs while peers keep trusting the original Evidence.
This page as .md · .json · CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.