CVE-2026-108361
Received Received - Intake

Runtime Code Modification in Privasys Remote Attestation TLS Clients

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

Publication date: 2026-10-12

Last updated on: 2026-10-12

Assigner: GitHub, Inc.

Description

Privasys Remote Attestation TLS Clients provides multi-language utilities for verifying attested TLS connections. Before 0.9.1, an attacker with local access could modify workload code, data, and configuration at any time after successful connection establishment. Once Evidence was successfully appraised and the connection was established, there was a window of vulnerability from the establishment of the connection to the termination of the connection where an attacker could modify the state of the workload and platform at runtime on the TLS endpoint acting as the Attester. This vulnerability was possible because Privasys/ra-tls-clients performed attestation only once in the lifetime of the connection (at connection establishment time), and the verifying peer continued to believe that the state was the same as in the initial Evidence throughout, whereas it could be stale at some point in time. This vulnerability is fixed in 0.9.1.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

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

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Privasys ra-tls-clients < 0.9.1

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-367 The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects Privasys Remote Attestation TLS Clients versions before 0.9.1. An attacker with local access could modify workload code, data, or configuration after a successful TLS connection was established. The system only performed attestation once at connection setup, so the verifying peer trusted the initial state even if it changed later. This created a window where the workload state could be altered without detection.

Detection Guidance

Detecting this vulnerability requires checking if Privasys ra-tls-clients versions before 0.9.1 are in use. Inspect installed packages or binaries for ra-tls-clients and verify the version against 0.9.1 or later. Monitor network connections for attested TLS sessions that do not enforce continuous attestation checks.

Impact Analysis

If you use Privasys ra-tls-clients before version 0.9.1, an attacker with local access could alter your workload's runtime state without detection. This could lead to unauthorized code execution, data tampering, or configuration changes, potentially compromising the security of your system.

Compliance Impact

This vulnerability could violate compliance requirements that mandate secure workload integrity and data protection, such as GDPR's security principles or HIPAA's integrity controls. Unauthorized runtime modifications may lead to data breaches or unauthorized access, risking non-compliance with these regulations.

Mitigation Strategies

Upgrade Privasys ra-tls-clients to version 0.9.1 or later to enable continuous attestation checks. Configure the TrustSelection option to 'fleet' mode for attested connections to ensure chain verification against fleet anchors. Disable unattested connections or ensure they use public PKI with hostname verification.

Chat Assistant

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

EPSS Chart