Private photo disclosure via permissive share-token fallback
Published Aug 25, 2026 · Updated Aug 25, 2026
Incorrect authorization in Liketrek TREK 3.0.0 through 3.0.22 allows remote attackers with a valid share token to read private photos. validateShareTokenForAsset returns the journey owner when an attacker-supplied asset ID is outside the shared journey, rather than denying access. Any valid journey share token reaches the public proxy, which streams the referenced asset from a connected Immich or Synology server with the owner's stored credentials; exploitation still requires knowing or obtaining an asset ID.
Summary
What happened
Incorrect authorization in Liketrek TREK 3.0.0 through 3.0.22 allows remote attackers with a valid share token to read private photos. validateShareTokenForAsset returns the journey owner when an attacker-supplied asset ID is outside the shared journey, rather than denying access. Any valid journey share token reaches the public proxy, which streams the referenced asset from a connected Immich or Synology server with the owner's stored credentials; exploitation still requires knowing or obtaining an asset ID.
The record
- CVE
- CVE-2026-78887
- Published
- Aug 25, 2026
- Updated
- Aug 25, 2026
- Vendor
- Liketrek
- Product
- TREK
- Classifications
- CWE-285, CWE-863, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 25, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0.0
- Affected versionversion=3.0.1
- Affected versionversion=3.0.10
- Affected versionversion=3.0.11
- Affected versionversion=3.0.12
- Affected versionversion=3.0.13
- Affected versionversion=3.0.14
- Affected versionversion=3.0.15
- Affected versionversion=3.0.16
- Affected versionversion=3.0.17
- Affected versionversion=3.0.18
- Affected versionversion=3.0.19
- Affected versionversion=3.0.2
- Affected versionversion=3.0.20
- Affected versionversion=3.0.21
- Affected versionversion=3.0.22
- Affected versionversion=3.0.3
- Affected versionversion=3.0.4
- Affected versionversion=3.0.5
- Affected versionversion=3.0.6
- Affected versionversion=3.0.7
- Affected versionversion=3.0.8
- Affected versionversion=3.0.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo