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-33537: CWE-918: Server-Side Request Forgery (SSRF) in LycheeOrg Lychee

0
Medium
VulnerabilityCVE-2026-33537cvecve-2026-33537cwe-918
Published: Thu Mar 26 2026 (03/26/2026, 20:01:19 UTC)
Source: CVE Database V5
Vendor/Project: LycheeOrg
Product: Lychee

Description

Lychee is a free, open-source photo-management tool. The patch introduced for GHSA-cpgw-wgf3-xc6v (SSRF via `Photo::fromUrl`) contains an incomplete IP validation check that fails to block loopback addresses and link-local addresses. Prior to version 7.5.1, an authenticated user can still reach internal services using direct IP addresses, bypassing all four protection configuration settings even when they are set to their secure defaults. Version 7.5.1 contains a fix for the issue.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/27/2026, 18:07:40 UTC

Technical Analysis

CVE-2026-33537 is a medium-severity SSRF vulnerability identified in Lychee, a popular open-source photo-management application. The vulnerability stems from an incomplete fix for a prior SSRF flaw (GHSA-cpgw-wgf3-xc6v) in the `Photo::fromUrl` function, where the IP validation logic fails to block loopback (e.g., 127.0.0.1) and link-local addresses (e.g., 169.254.0.0/16). This allows an authenticated user to craft requests that bypass all four protection configuration settings, even when set to their secure defaults, to reach internal services directly by IP address. Since SSRF vulnerabilities enable attackers to make the server perform unauthorized requests, this can lead to unauthorized access to internal network resources, potentially exposing sensitive data or enabling further attacks such as internal port scanning or exploitation of internal services. The vulnerability requires authentication but no user interaction beyond that, and the attack vector is network-based with low attack complexity. The issue affects all Lychee versions prior to 7.5.1, which contains the corrected IP validation logic. No public exploits have been reported yet, but the vulnerability is publicly disclosed and should be considered a significant risk for deployments exposing Lychee to untrusted authenticated users.

Potential Impact

This SSRF vulnerability can allow authenticated attackers to bypass network segmentation and access internal services that are otherwise protected from external access. Potential impacts include unauthorized access to sensitive internal APIs, databases, or administrative interfaces, leading to data leakage or further compromise of internal systems. Since Lychee is often deployed in environments managing private photo collections, the exposure of internal services could also lead to privacy violations or data integrity issues. The vulnerability could be leveraged to pivot attacks deeper into an organization's network, increasing the attack surface. Although exploitation requires authentication, many organizations have multiple users with access to Lychee, increasing the risk. The medium CVSS score reflects moderate impact and ease of exploitation, but the actual impact depends on the internal network architecture and the sensitivity of internal services accessible via SSRF.

Mitigation Recommendations

The primary mitigation is to upgrade Lychee to version 7.5.1 or later, which contains the fixed IP validation logic that blocks loopback and link-local addresses effectively. Until upgrading, organizations should restrict access to Lychee to trusted users only and limit network access from the Lychee server to internal services, implementing strict egress filtering and network segmentation to prevent SSRF exploitation. Additionally, administrators should review and harden internal services to require strong authentication and authorization, minimizing the impact if SSRF is exploited. Monitoring logs for unusual internal requests originating from Lychee can help detect exploitation attempts. Implementing Web Application Firewalls (WAFs) with SSRF detection rules may provide additional protection. Finally, educating users about the risks of uploading or linking to untrusted URLs can reduce attack vectors.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-20T18:05:11.831Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69c6c6933c064ed76fdc2997

Added to database: 3/27/2026, 6:04:03 PM

Last enriched: 3/27/2026, 6:07:40 PM

Last updated: 3/28/2026, 1:22:16 AM

Views: 5

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 for AI refresh and higher limits.

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

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses