Quick answers
- Is CVE-2026-61610 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-61610 being exploited in the wild.
- How severe is CVE-2026-61610?
- Informational severity, published 15 October 2026.
- Which products and versions are affected?
- LycheeOrg Lychee prior to 7.6.1.
- Is there a fix for CVE-2026-61610?
- Yes: fixed in 7.6.1. Until then: Disable or restrict the anonymous star-visibility feature if not required, as the vulnerability only affects installations using this non-default configuration. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-61610 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-61610?
- Check whether you run LycheeOrg Lychee at an affected version. 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.
How to fix
- Fixed in: 7.6.1
Disable or restrict the anonymous star-visibility feature if not required, as the vulnerability only affects installations using this non-default configuration.
Technical details
The vulnerability exists in the POST /api/v2/Photo::highlight endpoint, where PhotoPolicy::canHighlight() fails to check if the caller can view a photo before allowing the highlight operation. BaseApiRequest::validateResolved() performs authorization checks before checking visibility, allowing unauthenticated or anonymous users to modify photos in private or password-protected albums. An attacker can use differing HTTP response codes to distinguish between existing and non-existent photos.
Affected products
- LycheeOrg Lychee prior to 7.6.1
Timeline
- 2026-10-15: disclosed
- 2026-06-22: patched