Security readout for executives and security teams
Plain-English summary
TrustTunnel versions before 0.9.114 can let a permitted user reach internal or loopback network services despite private-network blocking being configured. The issue is a server-side request forgery bypass using numeric IP destinations. This can expose internal services through a VPN component and may affect integrity of reachable systems.
Executive priority
Prioritize remediation where TrustTunnel brokers access into sensitive internal networks. The fix is available, and the weakness can undermine network segmentation controls. Address internet-facing or broadly accessible deployments first.
Technical view
In tcp_forwarder.rs, TrustTunnel applied private-network SSRF checks only when the destination was parsed as a hostname. Numeric address destinations followed a separate path into TcpStream::connect() without equivalent loopback/private/global IP validation. CVSS is 7.1, high, with network access, low complexity, low privileges, and no user interaction.
Likely exposure
Exposure is limited to TrustTunnel deployments running versions earlier than 0.9.114, especially where tcp forwarding is enabled and allow_private_network_connections is expected to block internal access. An attacker needs low privileges according to the CVSS vector.
Exploitation context
The sources do not report active exploitation, and this CVE is not marked KEV in the provided data. Practical abuse would depend on attacker access to submit or influence forwarding destinations and the internal services reachable from the TrustTunnel server.
Researcher notes
Key evidence is the GitHub advisory and fixing commit. The root cause is inconsistent validation between hostname and numeric address destination handling. Do not assume broader product impact beyond TrustTunnel versions before 0.9.114 based on the provided sources.
Mitigation direction
- Upgrade TrustTunnel to version 0.9.114 or later.
- Restrict who can configure or request TCP forwarding destinations.
- Review vendor advisory and commit for deployment-specific guidance.
- Treat allow_private_network_connections=false as insufficient protection until upgraded.
Validation and detection
- Inventory TrustTunnel instances and record deployed versions.
- Confirm all affected instances are upgraded to 0.9.114 or later.
- Review forwarding configuration for private-network restrictions.
- Check available logs for numeric loopback or private destination attempts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-24902 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N2.84.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/TrustTunnel/TrustTunnel/security/advisories/GHSA-hgr9-frvw-5r76CVE reference · x_refsource_CONFIRM
- https://github.com/TrustTunnel/TrustTunnel/commit/734bb5cf103b72390a95c853cbf91e699cc01bc0CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.