# CVE-2026-40185: Missing Authorization on Immich Trip Photo Routes in TREK

> Attackers can access or modify trip photo management routes in TREK without proper authorization checks.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Apr 2026
- **Updated:** 15 Apr 2026
- **Also known as:** GHSA-pcr3-6647-jh72

## What is CVE-2026-40185?

CVE-2026-40185 is a high-severity missing authorization vulnerability in mauriceboe TREK, published on 10 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

TREK is a collaborative travel planner. Prior to 2.7.2, TREK was missing authorization checks on the Immich trip photo management routes. This vulnerability is fixed in 2.7.2.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Mauriceboe Trek.

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

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

## Is CVE-2026-40185 being exploited?

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

## Other vulnerabilities in mauriceboe TREK

- [CVE-2026-40184](https://insights.sbomify.com/CVE-2026-40184/): Unauthenticated Access to Uploaded Files in TREK (low 3.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40185 is a high-severity missing authorization vulnerability in mauriceboe TREK, published on 10 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-40185 in the wild and no public exploit code.

Affected product: mauriceboe 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-40185/ (Markdown: https://insights.sbomify.com/CVE-2026-40185/index.md)
```

## Sources

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

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