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.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
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
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.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-62679 being exploited?
There is no known exploitation of CVE-2026-62679 in the wild and no public exploit code.
Sources
Also known as GHSA-j5ff-34x8-xxqg.