# CVE-2026-61610: Lychee: unauthenticated photo starring reveals existence of private photos when photos_star_visibility=anonymous

> Unauthenticated attackers can reveal and modify private photos in Lychee when anonymous star visibility is enabled.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **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:** 20 Oct 2026
- **Also known as:** GHSA-qcqq-p4pq-7r77

## What is CVE-2026-61610?

CVE-2026-61610 is a low-severity missing authorization 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.1, when photos_star_visibility is set to anonymous, POST /api/v2/Photo::highlight can fetch and modify a photo without confirming that the caller can see it. BaseApiRequest::validateResolved() invokes SetPhotosHighlightedRequest::processValidatedValues() before authorization, and PhotoPolicy::canHighlight() returns true for anonymous callers without a canSee check. An unauthenticated attacker who can guess photo identifiers can distinguish existing private photos through differing success and not-found responses and can change their is_highlighted state, including for photos in private or password-protected albums. The issue is limited to installations using the non-default anonymous star-visibility setting. This issue is fixed in version 7.6.1.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-61610 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61610 is a low-severity missing authorization 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61610 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-61610/ (Markdown: https://insights.sbomify.com/CVE-2026-61610/index.md)
```

## Sources

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

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