# CVE-2026-78887: liketrek TREK Journey Photo Proxy validateShareTokenForAsset authorization

> Attackers can bypass authorization checks in the Journey Photo Proxy to access protected assets, requiring a software upgrade to fix.

- **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-24x9-fcj9-vp6w, GHSA-j7mw-g2xq-7xfh

## What is CVE-2026-78887?

CVE-2026-78887 is a medium-severity missing authorization 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 weakness has been identified in liketrek TREK up to 3.0.22. This impacts the function validateShareTokenForAsset of the component Journey Photo Proxy. Executing a manipulation can lead to incorrect authorization. The attack can be launched remotely. This attack is characterized by high complexity. The exploitability is said to be difficult. Upgrading to version 3.1.0 will fix this issue. You should upgrade the affected component.

Weakness: CWE-863 (Incorrect Authorization), CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-78887 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78887 is a medium-severity missing authorization 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-78887 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-78887/ (Markdown: https://insights.sbomify.com/CVE-2026-78887/index.md)
```

## Sources

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

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