TrustTunnel has SSRF and private network restriction bypass via numeric address destinations
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- Low · High · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA.
Summary
TrustTunnel is an open-source VPN protocol with a server-side request forgery and and private network restriction bypass in versions prior to 0.9.114. In `tcp_forwarder.rs`, SSRF protection for `allow_private_network_connections = false` was only applied in the `TcpDestination::HostName(peer)` path. The `TcpDestination::Address(peer) => peer` path proceeded to `TcpStream::connect()` without equivalent checks (for example `is_global_ip`, `is_loopback`), allowing loopback/private targets to be reached by supplying a numeric IP. The vulnerability is fixed in version 0.9.114.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| TrustTunnel | TrustTunnel | before 0.9.114 | 0.9.114 | Patch available | CNA |
- TrustTunnel VendorTrustTunnel Affected before 0.9.114 Fixed in 0.9.114 Patch available CNA
Remediation
- Fix · CNA TrustTunnel (TrustTunnel) Fixed in 0.9.114
Timeline
- 2026-10-02 Threatist record created from CVE-2026-24902
References
More Adguard Trusttunnel vulnerabilities
- TI-2026-20089 TrustTunnel has `client_random_prefix` rule bypass via fragmented or partial TLS ClientHello CVSS 3.1MEDIUM 5.3
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences