{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24904 exists.","fix":"No fix has been published for CVE-2026-24904 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-24904 is a medium-severity vulnerability in TrustTunnel, published on 29 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-24904 and fix it if it is affected.\n\nWhat it is: CVE-2026-24904 is a medium-severity vulnerability in TrustTunnel, published on 29 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24904 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-24904/ (Markdown: https://insights.sbomify.com/CVE-2026-24904/index.md)","id":"CVE-2026-24904","markdown":"https://insights.sbomify.com/CVE-2026-24904/index.md","name":"CVE-2026-24904","record":{"aliases":["GHSA-fqh7-r5gf-3r87"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"VPN protocol server","requires_auth":"none","summary":"Attackers can bypass client_random_prefix filtering rules in TrustTunnel by sending fragmented TLS ClientHello messages, allowing unauthorized traffic to pass through.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"trusttunnel","vendor":"adguard"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"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.","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 `client_random_prefix` rule bypass via fragmented or partial TLS ClientHello","id":"CVE-2026-24904","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Inspektor Gadget has a Command Injection vulnerability in Makefile.build","id":"CVE-2026-24905"},"packages":[],"prev":{"headline":"OrcaStatLLM Researcher Stored Cross-Site Scripting (XSS) via Log Message Injection in Session Page","id":"CVE-2026-24903"},"products":["TrustTunnel"],"published":"2026-01-29","related":[{"cvss_score":7.1,"headline":"TrustTunnel has SSRF and private network restriction bypass via numeric address destinations","id":"CVE-2026-24902","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-29","vendors":["TrustTunnel"]},"summary":"Attackers can bypass client_random_prefix filtering rules in TrustTunnel by sending fragmented TLS ClientHello messages, allowing unauthorized traffic to pass through.","url":"https://insights.sbomify.com/CVE-2026-24904/"}