CVE-2026-61610 — Lychee: unauthenticated photo starring reveals existence of private photos when photos_star_visibility=anonymous
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- No scoring signals.
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Lycheeorg Lychee).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 2.3 | CVSS 4.0 | Low | — | — | security-advisories@github.com via NIST National Vulnerability Database |
| 2.3 | CVSS 4.0 | Low | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X (score shown at the top: security-advisories@github.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Audit administrative actions and access to resources outside each user’s normal pattern.
Timeline
What happened to this CVE, newest first.
- 2026
- Source status changed · Received → Deferred
- Affected products added · lycheeorg/lychee
- Record published
- CVSS changed · 2.3
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 15, 2026 – Oct 15, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
4 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-77470 Lychee: Webshop checkout lets the client override the payment `amount` sent to the gateway via malicious crafted POST request 11h
- High CVE-2026-77466 Lychee: Webshop payment bypass via unrestricted "Dummy" gateway selection 11h
- High CVE-2026-77467 Lychee: A single 383-byte PDF causes ~184 seconds of CPU consumption in the real processing path 11h
- Medium CVE-2026-77468 Lychee: Missing Authentication for Critical Function and Allocation of Resources Without Limits or Throttling on /docs/api 11h
- High CVE-2026-62679 Lychee: Path traversal in `SecurePathController` allows authenticated arbitrary file read 11h
- High CVE-2026-61838 Lychee: Album password bypass in ZIP downloads 11h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-61610 is "Lychee: unauthenticated photo starring reveals existence of private photos when photos_star_visibility=anonymous", rated Low. It affects Lychee (Lycheeorg); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 2.3 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.