CVE-2026-56782
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGorse 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGorse before 0.5.10 has an authentication bypass in the /api/dump and /api/restore endpoints. When admin_api_key is left empty (the default configuration), these administrative endpoints accept requests without any authentication, allowing remote unauthenticated attackers to dump or restore the entire database including user PII.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Gorse installation and versionLocate the Gorse binary or service, then run 'gorse --version' or check the package version if installed via package managerAffected if Installed version is before 0.5.10
-
Locate Gorse configuration fileFind the config.toml or config.yaml file used by the Gorse instance (commonly in /etc/gorse/, the application directory, or the working directory)Affected if Configuration file exists and is accessible
-
Check admin_api_key configuration valueOpen the configuration file and inspect the admin_api_key setting under the [api] or [server] section. Verify whether it is set to a non-empty string or left blank/emptyAffected if The admin_api_key field is empty, missing, or set to an empty string ("")
-
Test vulnerable endpoint accessibilitySend an HTTP GET request to /api/dump or /api/restore without providing any API key (e.g., curl -k http://<host>:8088/api/dump)Affected if The endpoint returns a successful response with database data or accepts restore operations without authentication
You are affected if running Gorse version below 0.5.10 with an empty or unset admin_api_key configuration, and the /api/dump or /api/restore endpoints are accessible without credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Gorse to version 0.5.10 or later, or immediately set a strong non-empty admin_api_key in the configuration if upgrading is not feasible.
Gorse 0.5.10 or later
- Upgrade Gorse to version 0.5.10 or later, which contains the fix for this authentication bypass vulnerability
- After upgrading, verify that the /api/dump and /api/restore endpoints now require authentication
- If using Gorse in production, configure a non-empty admin_api_key in the configuration file to ensure authentication is enforced
- Restart the Gorse service after applying the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56782 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-56782 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data