Skip to main content

liketrek TREK CVE-2026-78886

| EUVDEUVD-2026-65474 MEDIUM
Path Traversal (CWE-22)
2026-08-25 VulDB GHSA-pw55-389h-h6rh
6.3
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify exposed TREK 3.0.x instance
  2. Delivery
    Target unauthenticated Public Journey Photo Proxy endpoint
  3. Exploit
    Craft traversal-encoded path payload
  4. Execution
    Bypass partial path sanitization logic
  5. Impact
    Read arbitrary files accessible to server process

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK

2 techniques across 2 tactics: Discovery, Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The target must be running liketrek TREK version 3.0.22 or earlier with the instance network-accessible to the attacker. The Public Journey Photo Proxy endpoint is publicly accessible by design (no session authentication required), as it exists to serve photos for unauthenticated public journey views - this is the structural condition enabling unauthenticated exploitation. High attack complexity (AC:H) indicates that exploitation is not trivial: the attacker likely requires knowledge of the server's internal directory structure and may need to employ specific path encoding or traversal bypass techniques to circumvent partial input validation. There is no requirement for a registered account, special server configuration, or non-default feature flag; the vulnerable endpoint exists in all standard TREK 3.0.x deployments. File read is limited to files readable by the TREK server process user.

Impact

The CVSS 4.0 score of 6.3 with AV:N/AC:H/PR:N/UI:N reflects a remotely reachable, unauthenticated attack surface paired with high exploitation complexity - meaning this is not a trivially weaponizable flaw. The confidentiality impact is bounded to Low (VC:L) with no integrity or availability impact, consistent with a read-only path traversal with limited file scope. No EPSS score was included in the available intelligence, so exploitation probability cannot be quantified beyond inference from CVSS metrics. The CVE is absent from the CISA KEV catalog and no public proof-of-concept code has been identified, keeping the realistic threat level moderate. TREK is a niche self-hosted product with a small deployment footprint, which further constrains aggregate risk at the population level; however, any single self-hosted operator who is externally exposing their instance should treat this as a prompt patching priority since the .env file and other sensitive configuration artifacts could be reachable. The high attack complexity suggests the traversal may require specific path encoding or knowledge of the server's directory layout, which is a meaningful limiting factor absent from the raw CVSS base score alone.

Exploit ScenarioDerived

An unauthenticated remote attacker sends a crafted HTTP GET request to the TREK Public Journey Photo Proxy endpoint, embedding path traversal sequences (e.g., ../../.env or URL-encoded equivalents) in the filename or path parameter. If the server's partial validation is bypassed through encoding tricks or specific path structures, the server returns the contents of files outside the media directory - potentially including the application's .env file containing database credentials or API keys. No public proof-of-concept exists at time of analysis, and the high attack complexity suggests some experimentation is required to identify the effective traversal payload.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 25, 2026

Path traversal in the liketrek TREK Public Journey Photo Proxy controller allows remote attackers - without authentication - to read files outside the intended directory on self-hosted instances running version 3.0.22 or earlier. The affected endpoint (server/src/nest/journey/journey-public.controller.ts) fails to adequately sanitize path inputs, exposing server-side files to limited confidentiality disclosure. No public exploit has been identified and the CVE is not listed in the CISA KEV catalog; a vendor-released patch is available in v3.1.0.

RemediationAI

The primary remediation is to upgrade liketrek TREK to version 3.1.0, the vendor-released patch available at https://github.com/liketrek/TREK/releases/tag/v3.1.0. This release fixes 18 privately-reported security vulnerabilities including this path traversal. Docker, Unraid, Helm, and manual install operators can upgrade immediately. Proxmox VE community-script users should hold at their current version until an updated LXC helper script is published to community-scripts.org and ProxmoxVED, as the 3.1.0 build layout changed to an npm workspaces monorepo and upgrading with the old script may corrupt the container; user data at /opt/trek/data, /opt/trek/uploads, and .env is safe in the interim. As a compensating control prior to patching, restrict external network access to the TREK instance using a reverse proxy with authentication enforcement in front of the public photo proxy route, or apply firewall rules limiting access to trusted IP ranges - noting that this will break the unauthenticated public journey sharing feature by design.

Affected VersionsENISA

TREK 3.0.1
TREK 3.0.21
TREK 3.0.15
TREK 3.0.5
TREK 3.0.7
TREK 3.0.13
TREK 3.0.10
TREK 3.0.20
TREK 3.0.11
TREK 3.0.18
TREK 3.0.17
TREK 3.0.9
TREK 3.0.4
TREK 3.0.14
TREK 3.0.22
TREK 3.0.19
TREK 3.0.8
TREK 3.0.12
TREK 3.0.6
TREK 3.0.3
TREK 3.0.0
TREK 3.0.2
TREK 3.0.16

Affected Packages

euvd trek no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

TREK is a self-hosted travel journal application. Prior to v3.1.0, the backend ran on Express; v3.1.0 migrated to NestJS. The vulnerable component is the Public Journey Photo Proxy, a NestJS controller (server/src/nest/journey/journey-public.controller.ts) that serves photos associated with public journey views without requiring authentication. CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) indicates the controller does not canonicalize or sufficiently validate file path inputs supplied by the caller, allowing directory traversal sequences such as ../ to escape the intended upload or media directory. The CPE cpe:2.3:a:liketrek:trek:*:*:*:*:*:*:*:* covers all Trek versions up to and including 3.0.22.

Know when Trek gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 6.3 MEDIUM
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 3.7 LOW

Network-reachable public endpoint with no authentication (AV:N, PR:N) but high exploitation complexity (AC:H); only limited file read is achievable (C:L) with no integrity or availability impact.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
High
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

A security flaw has been discovered in liketrek TREK up to 3.0.22. This affects an unknown function of the file server/src/nest/journey/journey-public.controller.ts of the component Public Journey Photo Proxy. Performing a manipulation results in path traversal. The attack can be initiated remotely. The attack's complexity is rated as high. The exploitability is reported as difficult. Upgrading to version 3.1.0 mitigates this issue. It is advisable to upgrade the affected component.

Threat Intelligence Overview

EPSS Score
0.4%
Top 65% exploitable
Prevalence
Rare
niche self-hosted travel journal, small community deployment
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

More in Trek

View all
CVE-2026-77294 HIGH
8.1 Sep 24

Server-side request forgery in TREK before 3.3.0 allows an authenticated user (CVSS PR:L) to persist an attacker-control

CVE-2026-40185 HIGH
7.1 Apr 10

Authentication bypass in TREK collaborative travel planner (versions prior to 2.7.2) allows authenticated attackers with

CVE-2026-77293 HIGH
7.1 Sep 24

TREK, a collaborative travel-planning web application, authorizes the DELETE /api/trips/:tripId/collab/notes/:noteId/fil

CVE-2026-54509 MEDIUM
6.5 Aug 20

Share-link token theft in TREK versions 3.0.0 through 3.0.x allows any ordinary authenticated user to exfiltrate private

CVE-2026-78885 MEDIUM
6.3 Aug 25

Improper authentication in liketrek TREK up to version 3.0.22 allows a remote unauthenticated attacker to bypass the OID

CVE-2026-85738 MEDIUM
6.3 Sep 24

Server-side request forgery in TREK (versions prior to 3.4.0) allows an authenticated user to reach internal services or

CVE-2026-78887 MEDIUM
6.3 Aug 25

Incorrect authorization in liketrek TREK's Journey Photo Proxy (all versions through 3.0.22) enables remote unauthentica

CVE-2026-54508 MEDIUM
5.3 Aug 20

Server-Side Request Forgery in TREK, a collaborative travel planner, allows any authenticated user to pivot the server i

CVE-2026-78863 MEDIUM
5.3 Aug 25

Authentication bypass in liketrek TREK up to v3.0.22 allows a remote attacker with valid credentials to circumvent two-f

CVE-2026-77320 MEDIUM
5.3 Sep 24

TREK, a self-hosted collaborative travel planner, returns complete trip itinerary data - day plans, assignments, notes,

CVE-2026-78864 MEDIUM
5.3 Aug 25

SQL injection in liketrek TREK's Journey Entry Update endpoint allows authenticated remote attackers to manipulate under

CVE-2026-62945 MEDIUM
4.3 Aug 20

Insecure direct object reference in TREK collaborative travel planner before 3.1.3 allows any authenticated user with fi

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy