# CVE-2026-62679: Lychee: Path traversal in `SecurePathController` allows authenticated arbitrary file read

> Authenticated attackers can read arbitrary files via path traversal in Lychee when specific non-default configurations are enabled, potentially exposing credentials.

- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:H`)
- **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:** 15 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-j5ff-34x8-xxqg

## What is CVE-2026-62679?

CVE-2026-62679 is a high-severity path traversal vulnerability in LycheeOrg Lychee, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Lychee is a free, open-source photo-management tool. Prior to 7.6.4, SecurePathController, which serves GET /image/{path}, concatenates the attacker-controlled path with the local storage root and performs a string-prefix check before canonicalizing dot segments. Under the supported non-default configuration with temporary_image_link_enabled enabled, temporary_image_link_when_logged_in disabled, and secure_image_link_enabled disabled, any authenticated user can submit encoded traversal segments that pass the prefix check and are later resolved by filesystem operations. This permits reading files available to the web process, including application configuration and other users' private images, and disclosed APP_KEY or database credentials can enable further compromise. This issue is fixed in version 7.6.4.

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

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


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

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

## Is CVE-2026-62679 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-62679 is a high-severity path traversal vulnerability in LycheeOrg Lychee, published on 15 Oct 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-62679 in the wild and no public exploit code.

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

## Sources

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

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