Vulnerability in TREK (CVE-2026-45410)
Summary
Vulnerability in TREK (CVE-2026-45410). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.0.18 or later.
Original description
The description as published by the source.
TREK is a collaborative travel planner. Prior to 3.0.18, early return on missing user during login flow allowed an attacker to enumerate valid user accounts via response timing discrepancy. When an email address existed in the database, the backend performed a bcrypt password comparison before returning a 401 Unauthorized, adding ~370 ms of latency. When the email did not exist, the backend returned immediately (~10 ms). This ~14× timing difference could be detected without any difference in HTTP status codes or response bodies. This vulnerability is fixed in 3.0.18.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45410 has been found in TREK.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade TREK to 3.0.18 or later.
If unsure, ask your IT team or search "TREK CVE-2026-45410" on the vendor's site.
CVE-2026-45410 (TREK) — CWE-203 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.0.18 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-203) exists in TREK.
Check the vendor advisory for the affected versions of TREK.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 3.0.18.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'TREK' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'TREK' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
TREKを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade TREK to 3.0.18ステージング環境で 3.0.18 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- web gist.github.com