# CVE-2026-77468: Missing authorization in Lychee

> Unauthenticated access to API documentation allows attackers to map the API surface and cause denial of service via resource exhaustion.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-xg8r-4pm3-2h4f

## What is CVE-2026-77468?

CVE-2026-77468 is a medium-severity missing authorization vulnerability in LycheeOrg Lychee, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Lychee is a free, open-source photo-management tool. Prior to 7.7.0, GET /docs/api exposes the Scramble-generated OpenAPI documentation configured by config/scramble.php to unauthenticated callers after installation, with observed response size and latency suggesting that the schema is regenerated without an application-level cache. A remote attacker can repeatedly request the unthrottled route to consume server CPU and obtain a detailed map of the API surface and parameter schema. This issue is fixed in version 7.7.0.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

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

## Is CVE-2026-77468 being exploited?

There is no known exploitation of CVE-2026-77468 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77468 is a medium-severity missing authorization vulnerability in LycheeOrg Lychee, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-77468 in the wild and no public exploit code.

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-77468/ (Markdown: https://insights.sbomify.com/CVE-2026-77468/index.md)
```

## Sources

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

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