CVE-2026-40185: mauriceboe TREK missing authorization in Immich photo routes

CVE-2026-40185 · Severity: high · CVSS 7.1 · Published 2026-04-10

TREK is a collaborative travel planning application. A security flaw in versions prior to 2.7.2 allowed any logged-in user to view or modify photos and album links belonging to other users' private trips. This could lead to the unauthorized exposure of personal travel photos and the modification of trip data.

Technologies: Mauriceboe Trek. Vendors: Mauriceboe.

Quick answers

Is CVE-2026-40185 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-40185 being exploited in the wild.
How severe is CVE-2026-40185?
High severity, with a CVSS score of 7.1, published 10 April 2026.
Which products and versions are affected?
mauriceboe TREK < 2.7.2.
Is there a fix for CVE-2026-40185?
A patch was published on 2026-04-01: Fix released in version 2.7.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-40185 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-40185?
Check whether you run Mauriceboe Trek. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A missing authorization vulnerability (CWE-862) exists in TREK's Immich integration routes. Specifically, the application failed to perform 'canAccessTrip' checks on endpoints including GET/POST/DELETE /trips/:tripId/photos and related album-link routes. An authenticated attacker could exploit this by supplying a trip ID belonging to another user, allowing them to view, add, or delete photos and manage sharing links. The vulnerability is resolved in version 2.7.2 by enforcing proper membership validation for all trip-related photo management requests.

Affected products

  • mauriceboe TREK < 2.7.2

Timeline

  • 2026-04-01: patched: Fix released in version 2.7.2
  • 2026-04-10: disclosed: Initial CVE publication
  • 2026-04-21: advisory: NVD analysis updated

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.