{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24902 exists.","fix":"No fix has been published for CVE-2026-24902 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-24902 is a high-severity server-side request forgery vulnerability in TrustTunnel, published on 29 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-24902 and fix it if it is affected.\n\nWhat it is: CVE-2026-24902 is a high-severity server-side request forgery vulnerability in TrustTunnel, published on 29 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24902 exists.\n\nAffected product: TrustTunnel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-24902/ (Markdown: https://insights.sbomify.com/CVE-2026-24902/index.md)","id":"CVE-2026-24902","markdown":"https://insights.sbomify.com/CVE-2026-24902/index.md","name":"CVE-2026-24902","record":{"aliases":["GHSA-hgr9-frvw-5r76"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"VPN server software","requires_auth":"low_privilege","summary":"Attackers can bypass private network restrictions and access internal services via numeric IP addresses in TrustTunnel when SSRF protection is enabled.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"trusttunnel","vendor":"adguard"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"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) =\u003e 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"TrustTunnel has SSRF and private network restriction bypass via numeric address destinations","id":"CVE-2026-24902","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"OrcaStatLLM Researcher Stored Cross-Site Scripting (XSS) via Log Message Injection in Session Page","id":"CVE-2026-24903"},"packages":[],"prev":{"headline":"Outline's IDOR allows unauthorized viewing and seizing of private deleted drafts","id":"CVE-2026-24901"},"products":["TrustTunnel"],"published":"2026-01-29","related":[{"cvss_score":5.3,"headline":"TrustTunnel has `client_random_prefix` rule bypass via fragmented or partial TLS ClientHello","id":"CVE-2026-24904","kev_date_added":null,"published":"2026-01-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-29","vendors":["TrustTunnel"]},"summary":"Attackers can bypass private network restrictions and access internal services via numeric IP addresses in TrustTunnel when SSRF protection is enabled.","url":"https://insights.sbomify.com/CVE-2026-24902/"}