Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 20 Feb 2026 21:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Adguard
Adguard trusttunnel |
|
| CPEs | cpe:2.3:a:adguard:trusttunnel:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Adguard
Adguard trusttunnel |
Fri, 30 Jan 2026 09:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Trusttunnel
Trusttunnel trusttunnel |
|
| Vendors & Products |
Trusttunnel
Trusttunnel trusttunnel |
Thu, 29 Jan 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 29 Jan 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | TrustTunnel has SSRF and private network restriction bypass via numeric address destinations | |
| Weaknesses | CWE-918 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-01-29T21:33:10.256Z
Reserved: 2026-01-27T19:35:20.530Z
Link: CVE-2026-24902
Updated: 2026-01-29T21:33:05.970Z
Status : Analyzed
Published: 2026-01-29T22:15:54.893
Modified: 2026-02-20T20:57:04.633
Link: CVE-2026-24902
No data.
OpenCVE Enrichment
Updated: 2026-04-18T01:30:16Z