Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-22784: CWE-863: Incorrect Authorization in LycheeOrg Lychee

0
Low
VulnerabilityCVE-2026-22784cvecve-2026-22784cwe-863
Published: Mon Jan 12 2026 (01/12/2026, 18:37:55 UTC)
Source: CVE Database V5
Vendor/Project: LycheeOrg
Product: Lychee

Description

Lychee is a free, open-source photo-management tool. Prior to 7.1.0, an authorization vulnerability exists in Lychee's album password unlock functionality that allows users to gain possibly unauthorized access to other users' password-protected albums. When a user unlocks a password-protected public album, the system automatically unlocks ALL other public albums that share the same password, resulting in a complete authorization bypass. This vulnerability is fixed in 7.1.0.

AI-Powered Analysis

AILast updated: 01/12/2026, 19:09:10 UTC

Technical Analysis

CVE-2026-22784 is an authorization vulnerability classified under CWE-863 (Incorrect Authorization) found in Lychee, a free and open-source photo-management application. The vulnerability exists in versions prior to 7.1.0 and relates to the album password unlock functionality. When a user successfully unlocks a password-protected public album, the system erroneously unlocks all other public albums that share the same password. This behavior results in an authorization bypass, allowing users to access albums they should not be authorized to view. The vulnerability does not require the user to have any privileges or prior authentication but does require user interaction to unlock at least one album. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), user interaction required (UI:P), and low confidentiality impact (VC:L), with no impact on integrity or availability. No known exploits have been reported in the wild. The issue was publicly disclosed on January 12, 2026, and fixed in Lychee version 7.1.0. The root cause is the shared password mechanism that treats all albums with the same password as unlocked once one is accessed, violating proper authorization checks. This can lead to unauthorized disclosure of private photo albums, potentially exposing sensitive or personal information.

Potential Impact

For European organizations using Lychee to manage photo collections, this vulnerability could lead to unauthorized disclosure of sensitive or private images stored in password-protected albums. Although the impact is limited to confidentiality and does not affect data integrity or system availability, unauthorized access to private media can have privacy, reputational, and compliance implications, especially under GDPR regulations. Organizations that use Lychee for internal or customer-facing photo management services may face data privacy breaches if attackers exploit this flaw. The requirement for user interaction reduces the risk of automated exploitation, but insider threats or social engineering could facilitate unauthorized access. Since the vulnerability affects only albums sharing the same password, reuse of passwords across multiple albums increases the scope of exposure. The low CVSS score reflects the limited severity, but the privacy impact can still be significant depending on the nature of the photos stored.

Mitigation Recommendations

The primary mitigation is to upgrade Lychee installations to version 7.1.0 or later, where the authorization bypass is fixed. Until upgrades are applied, organizations should audit their album password policies to ensure unique passwords are used per album to minimize the risk of mass unauthorized access. Administrators should educate users about the risks of password reuse across albums. Additionally, consider disabling public album password protection if not strictly necessary or implement alternative access control mechanisms. Monitoring access logs for unusual unlocking patterns can help detect potential exploitation attempts. Organizations should also review their data privacy policies and ensure that any exposed data is handled in compliance with GDPR and other relevant regulations. Finally, maintain awareness of any future exploit reports or patches related to this vulnerability.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-09T18:27:19.388Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6965433ada2266e838fe6b32

Added to database: 1/12/2026, 6:53:46 PM

Last enriched: 1/12/2026, 7:09:10 PM

Last updated: 1/13/2026, 12:53:59 AM

Views: 9

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats