Quick answers
- Is CVE-2026-61611 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-61611 being exploited in the wild.
- How severe is CVE-2026-61611?
- High severity, with a CVSS score of 7.5, published 15 October 2026.
- Which products and versions are affected?
- LycheeOrg Lychee prior to 7.6.1.
- Is there a fix for CVE-2026-61611?
- Yes: fixed in 7.6.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-61611 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-61611?
- 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
Technical details
The POST /api/v2/Album::unlock endpoint lacked throttling, attempt counters, backoff mechanisms, or CAPTCHAs. The UnlockAlbumRequest::authorize() method permitted any unauthenticated caller to submit attempts, and Hash::check() verified each guess without limiting repeated failures. The vulnerability was fixed by adding rate limiting middleware (throttle:10,1) restricting requests to 10 per minute.
Affected products
- LycheeOrg Lychee prior to 7.6.1
Timeline
- 2026-10-15: disclosed
- 2026-06-22: patched