# CVE-2026-61611: Lychee: Missing rate limiting on album password unlock endpoint allows brute-force attacks

> Remote attackers can brute-force album passwords due to missing rate limiting, gaining unauthorized access to private photo collections.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-48vf-fwx6-2ph6

## What is CVE-2026-61611?

CVE-2026-61611 is a high-severity missing authorization vulnerability in LycheeOrg Lychee, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Lychee is a free, open-source photo-management tool. Prior to 7.6.1, POST /api/v2/Album::unlock has no throttle, attempt counter, backoff, CAPTCHA, or lockout. UnlockAlbumRequest::authorize() permits any caller to submit attempts, and app/Actions/Album/Unlock.php verifies each guess with Hash::check without limiting repeated failures. A remote unauthenticated attacker who knows or can obtain an album identifier can automate password guesses against a password-protected album and, if the password is recovered, gain access to its private photo collection. This issue is fixed in version 7.6.1.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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


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

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

## Is CVE-2026-61611 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61611 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61611 is a high-severity missing authorization vulnerability in LycheeOrg Lychee, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61611 exists.

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

## Sources

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

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