Quick answers
- Is CVE-2026-108361 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108361 being exploited in the wild.
- How severe is CVE-2026-108361?
- Informational severity, published 12 October 2026.
- Which products and versions are affected?
- Privasys Remote Attestation TLS Clients before 0.9.1.
- Is there a fix for CVE-2026-108361?
- Yes: fixed in 0.9.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-108361 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-108361?
- Check whether you run Privasys Remote Attestation TLS Clients at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.9.1
Technical details
The vulnerability is a missing re-attestation issue in ra-tls-clients versions before 0.9.1. Attestation is performed only at connection establishment time, after which no further verification occurs, allowing an attacker with local access to modify workload code, data, configuration, or platform state without detection. The fix introduces challenge-mode re-attestation that verifies the state remains unchanged throughout the connection lifetime.
Affected products
- Privasys Remote Attestation TLS Clients before 0.9.1
Timeline
- 2026-10-12: disclosed