# CVE-2026-77466: Lychee: Webshop payment bypass via unrestricted "Dummy" gateway selection

> Attackers can bypass payment validation in Lychee webshop by selecting a dummy gateway, potentially obtaining paid items without payment.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/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:** 15 Oct 2026
- **Also known as:** GHSA-5wh2-hg7q-6hv3

## What is CVE-2026-77466?

CVE-2026-77466 is a high-severity 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, Lychee hides the Omnipay Dummy test provider from the checkout options in production through OmnipayFactory::get_supported_providers(), but CreateSessionRequest validates only that the submitted provider is an OmnipayProviderType and does not enforce OmnipayProviderType::isAllowed(). A buyer, including a guest when webshop_allow_guest_checkout is enabled, can submit Dummy directly and complete the test gateway flow without a real payment. When webshop_auto_fulfill_enabled is enabled, OrderCompletedListener::fullfillOrder() can then release the purchasable item. The issue requires access to the Supporter or Pro webshop and an enabled purchasable item. Testing bypassed the closed-source license middleware, so whether the real license layer performs additional payment-provider validation remains unverified. The payment finalize status check itself is not the root cause. This issue is fixed in version 7.7.0.

Weakness: CWE-20 (Improper Input Validation), CWE-184 (Incomplete List of Disallowed Inputs)

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


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

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

## Is CVE-2026-77466 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77466 is a high-severity 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77466 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-77466/ (Markdown: https://insights.sbomify.com/CVE-2026-77466/index.md)
```

## Sources

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

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