# CVE-2026-56782: Gorse - Unauthenticated Database Dump and Restore via /api/dump and /api/restore Endpoints

> Unauthenticated attackers can dump or restore the entire database via API endpoints when the admin key is empty, exposing sensitive data and allowing dataset overwrites.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 29 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-65p2-39gr-3m25

## What is CVE-2026-56782?

CVE-2026-56782 is a critical authentication bypass vulnerability in gorse-io gorse, published on 29 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Gorse before 0.5.10 contains an authentication bypass vulnerability in the /api/dump and /api/restore endpoints that allows unauthenticated attackers to access protected functionality when admin_api_key is empty, which is the default configuration. Remote attackers can exfiltrate the entire database including user records, items, and feedback data containing personally identifiable information, or completely overwrite the dataset without authentication.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-56782 being exploited?

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

Public exploit code:

- CVE-2026-56782 — Gorse <0.5.10 unauthenticated DB dump/restore (admin_api_key fail-open). Lab + PoC, verified e2e. (github_poc): https://github.com/BiiTts/CVE-2026-56782-Gorse-Auth-Bypass
- Gorse < 0.5.10 - Unauthenticated Database Dump (nuclei): http/cves/2026/CVE-2026-56782.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56782 is a critical authentication bypass vulnerability in gorse-io gorse, published on 29 Jun 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-56782 exists.

Affected product: gorse-io gorse. 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-56782/ (Markdown: https://insights.sbomify.com/CVE-2026-56782/index.md)
```

## Sources

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

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