Description
Lychee is a free, open-source photo-management tool. Prior to 7.6.0, the POST /api/v2/Photo::fromUrl flow validates a hostname and its resolved addresses in app/Rules/PhotoUrlRule.php but later passes the original hostname through app/Actions/Import/FromUrl.php to app/Image/Files/DownloadedFile.php for a separate fopen connection. An authenticated attacker who controls DNS responses can cause validation to observe a public address and the subsequent fetch to resolve the same hostname to a private or otherwise forbidden address. This DNS rebinding time-of-check to time-of-use mismatch bypasses the intended server-side request forgery protections and can reach services available from the Lychee server, subject to deployment and TLS behavior. This issue is fixed in version 7.6.0.
Published: 2026-10-15
Score: 2.3 Low
EPSS: < 1% Very Low
KEV: No
Impact: Server Side Request Forgery
Action: Patch
AI Analysis

Impact

Lychee’s Photo::fromUrl endpoint validates a hostname and its resolved addresses before download, but later re‑uses the original hostname when opening the file. This flaw allows an authenticated attacker who can control DNS responses to force the server to obtain a public address during validation and later resolve the same hostname to a private or otherwise restricted IP. The attacker can use this to query internal services from the Lychee host, bypassing the intended server‑side request forgery controls. The vulnerability is thus a Server Side Request Forgery (SSRF) that can expose internal network resources.

Affected Systems

Lychee versions before 7.6.0 are affected. The affected product is Lychee.org’s Lychee photo‑management application; any deployment using a version earlier than 7.6.0 without the 7.6.0 patch is at risk.

Risk and Exploitability

The vulnerability has a CVSS score of 2.3, indicating low severity, and an EPSS score of less than 1%, suggesting a very low probability of exploitation. It is not listed in the CISA KEV catalog. Exploitation requires an authenticated user and the ability to influence DNS resolution for the target hostname. The likely attack path involves the attacker owning or controlling the DNS records for a hostname passed to Photo::fromUrl, causing the Lychee server to resolve to an internal IP after initial validation passed. Under these conditions the server can reach services that are only accessible from the internal network.

Generated by OpenCVE AI on October 16, 2026 at 20:13 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Lychee to version 7.6.0 or later, which removes the flaw by properly pinning the resolved IP address during validation.
  • If an upgrade is not immediately possible, configure the server to reject DNS responses that resolve to private IP ranges during the import process, or otherwise restrict the import endpoint to trusted hostnames only.
  • Implement network-level controls such as a firewall rule to block outbound connections from the Lychee host to private networks or ensure that only HTTPS traffic is allowed for outbound requests when using the Photo::fromUrl feature.

Generated by OpenCVE AI on October 16, 2026 at 20:13 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 17 Oct 2026 19:15:00 +0000

Type Values Removed Values Added
First Time appeared Lycheeorg
Lycheeorg lychee
Vendors & Products Lycheeorg
Lycheeorg lychee

Thu, 15 Oct 2026 18:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 15 Oct 2026 16:45:00 +0000

Type Values Removed Values Added
Description Lychee is a free, open-source photo-management tool. Prior to 7.6.0, the POST /api/v2/Photo::fromUrl flow validates a hostname and its resolved addresses in app/Rules/PhotoUrlRule.php but later passes the original hostname through app/Actions/Import/FromUrl.php to app/Image/Files/DownloadedFile.php for a separate fopen connection. An authenticated attacker who controls DNS responses can cause validation to observe a public address and the subsequent fetch to resolve the same hostname to a private or otherwise forbidden address. This DNS rebinding time-of-check to time-of-use mismatch bypasses the intended server-side request forgery protections and can reach services available from the Lychee server, subject to deployment and TLS behavior. This issue is fixed in version 7.6.0.
Title Lychee: Distinct post-fix SSRF variant in Photo::fromUrl due to missing IP pinning after DNS-based validation
Weaknesses CWE-367
CWE-918
References
Metrics cvssV4_0

{'score': 2.3, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:L'}


Subscriptions

Lycheeorg Lychee
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-10-15T17:58:10.062Z

Reserved: 2026-06-24T18:49:56.207Z

Link: CVE-2026-57569

cve-icon Vulnrichment

Updated: 2026-10-15T17:57:59.137Z

cve-icon NVD

Status : Deferred

Published: 2026-10-15T17:17:24.033

Modified: 2026-10-15T21:08:49.703

Link: CVE-2026-57569

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-17T19:00:13Z

Weaknesses
  • CWE-367

    Time-of-check Time-of-use (TOCTOU) Race Condition

  • CWE-918

    Server-Side Request Forgery (SSRF)