# CVE-2026-78886: liketrek TREK Public Journey Photo Proxy journey-public.controller.ts path traversal

> Remote attackers can exploit a path traversal flaw in the Public Journey Photo Proxy to read arbitrary files, requiring high complexity and permissions.

- **Severity:** Medium 6.3 (`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/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-h66w-m5g2-cqpc, GHSA-pw55-389h-h6rh

## What is CVE-2026-78886?

CVE-2026-78886 is a medium-severity path traversal vulnerability in liketrek TREK, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-78886?


## How do I fix CVE-2026-78886?

No fix has been published for CVE-2026-78886 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-78886 being exploited?

There is no known exploitation of CVE-2026-78886 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-78886 and fix it if it is affected.

What it is: CVE-2026-78886 is a medium-severity path traversal vulnerability in liketrek TREK, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-78886 in the wild and no public exploit code.

Affected product: liketrek TREK. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-78886/ (Markdown: https://insights.sbomify.com/CVE-2026-78886/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-78886
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-78886
- OSV: https://osv.dev/vulnerability/CVE-2026-78886

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-78886/
Summaries are generated and may contain mistakes; the official description above is the record.