CVE-2026-56782
Auth bypass on Gorse API enables unauthenticated DB access and data manipulation.
Is CVE-2026-56782 being exploited?
Not confirmed. CVE-2026-56782 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 3.6% probability of exploitation in the next 30 days.
How severe is CVE-2026-56782?
CVE-2026-56782 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-56782?
Yes. A fix has been recorded for CVE-2026-56782. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-56782 affect?
CVE-2026-56782 affects Gorse. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-56782?
Upgrade to 0.5.10+ or apply patch; configure admin_api_key and disable the default.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Exfiltration of full DB (PII) or overwrite data via unauthenticated /api/dump and /api/restore.
Immediate action required
- affected< 0.5.10
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.