# CVE-2026-57569: Lychee: Distinct post-fix SSRF variant in Photo::fromUrl due to missing IP pinning after DNS-based validation

> An authenticated attacker can bypass SSRF protections via DNS rebinding to access internal services from the Lychee server.

- **Severity:** Low 2.3 (`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`)
- **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:** 15 Oct 2026
- **Also known as:** GHSA-vj35-v9x5-vrxh

## What is CVE-2026-57569?

CVE-2026-57569 is a low-severity server-side request forgery 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.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.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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


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

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

## Is CVE-2026-57569 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-57569 is a low-severity server-side request forgery 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-57569 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-57569/ (Markdown: https://insights.sbomify.com/CVE-2026-57569/index.md)
```

## Sources

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

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