CVE-2026-24904

TrustTunnel is an open-source VPN protocol with a rule bypass issue in versions prior to 0.9.115. In `tls_listener.rs`, `TlsListener::listen()` peeks 1024 bytes and calls `extract_client_random(...)`. If `parse_tls_plaintext` fails (for example, a fragmented/partial ClientHello split across TCP writes), `extract_client_random` returns `None`. In `rules.rs`, `RulesEngine::evaluate` only evaluates `client_random_prefix` when `client_random` is `Some(...)`. As a result, when extraction fails (`client_random == None`), any rule that relies on `client_random_prefix` matching is skipped and evaluation falls through to later rules. As an important semantics note: `client_random_prefix` is a match condition only. It does not mean "block non-matching prefixes" by itself. A rule with `client_random_prefix = ...` triggers its `action` only when the prefix matches (and the field is available to evaluate). Non-matches (or `None`) simply do not match that rule and continue to fall through. The vulnerability is fixed in version 0.9.115.
Configurations

Configuration 1 (hide)

cpe:2.3:a:adguard:trusttunnel:*:*:*:*:*:*:*:*

History

17 Jun 2026, 10:23

Type Values Removed Values Added
References () https://github.com/TrustTunnel/TrustTunnel/security/advisories/GHSA-fqh7-r5gf-3r87 - Exploit, Vendor Advisory, Patch () https://github.com/TrustTunnel/TrustTunnel/security/advisories/GHSA-fqh7-r5gf-3r87 - Exploit, Patch, Vendor Advisory
Summary
  • (es) TrustTunnel es un protocolo VPN de código abierto con un problema de omisión de reglas en versiones anteriores a la 0.9.115. En `tls_listener.rs`, `TlsListener::listen()` examina 1024 bytes y llama a `extract_client_random(...)`. Si `parse_tls_plaintext` falla (por ejemplo, un ClientHello fragmentado/parcial dividido en varias escrituras TCP), `extract_client_random` devuelve `None`. En `rules.rs`, `RulesEngine::evaluate` solo evalúa `client_random_prefix` cuando `client_random` es `Some(...)`. Como resultado, cuando la extracción falla (`client_random == None`), cualquier regla que dependa de la coincidencia de `client_random_prefix` se omite y la evaluación pasa a reglas posteriores. Como una nota semántica importante: `client_random_prefix` es solo una condición de coincidencia. No significa 'bloquear prefijos no coincidentes' por sí mismo. Una regla con `client_random_prefix = ...` activa su `acción` solo cuando el prefijo coincide (y el campo está disponible para evaluar). Las no-coincidencias (o `None`) simplemente no coinciden con esa regla y continúan pasando. La vulnerabilidad está corregida en la versión 0.9.115.

20 Feb 2026, 20:58

Type Values Removed Values Added
First Time Adguard trusttunnel
Adguard
References () https://github.com/TrustTunnel/TrustTunnel/commit/aa5060145506952b9431b0ed3edb52bb6c08d9a6 - () https://github.com/TrustTunnel/TrustTunnel/commit/aa5060145506952b9431b0ed3edb52bb6c08d9a6 - Patch
References () https://github.com/TrustTunnel/TrustTunnel/security/advisories/GHSA-fqh7-r5gf-3r87 - () https://github.com/TrustTunnel/TrustTunnel/security/advisories/GHSA-fqh7-r5gf-3r87 - Exploit, Vendor Advisory, Patch
CPE cpe:2.3:a:adguard:trusttunnel:*:*:*:*:*:*:*:*

29 Jan 2026, 22:15

Type Values Removed Values Added
New CVE

Information

Published : 2026-01-29 22:15

Updated : 2026-06-17 10:23


NVD link : CVE-2026-24904

Mitre link : CVE-2026-24904

CVE.ORG link : CVE-2026-24904


JSON object : View

Products Affected

adguard

  • trusttunnel
CWE
CWE-284

Improper Access Control