Quick answers
- Is CVE-2026-75846 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-75846 being exploited in the wild.
- How severe is CVE-2026-75846?
- High severity, with a CVSS score of 7.1, published 18 August 2026.
- Which products and versions are affected?
- ArcadeData ArcadeDB before 26.8.1; affected versions <= 26.7.3.
- Is there a fix for CVE-2026-75846?
- A patch was published on 2026-08-18: Fixed in version 26.8.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-75846 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-75846?
- Check whether you run ArcadeData ArcadeDB at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a missing authorization check (CWE-862) in the DELETE FUNCTION SQL statement handler (DeleteFunctionStatement.executeSimple). The vulnerable code fails to call checkPermissionsOnDatabase(UPDATE_SCHEMA) before unregistering and persisting deletion of server-side functions to the database schema. Any authenticated database user can exploit this via the POST /api/v1/command/{db} API endpoint to permanently remove any registered function, including security-relevant logic. The root cause is that unregisterFunction() in both PolyglotFunctionLibraryDefinition and SQLFunctionLibraryDefinition lacks permission guards, while similar operations (unregisterFunctionLibrary) are properly protected. The fix is to add the missing authorization check at the start of DeleteFunctionStatement.executeSimple.
Affected products
- ArcadeData ArcadeDB before 26.8.1; affected versions <= 26.7.3
Timeline
- 2026-08-18: disclosed
- 2026-08-18: patched: Fixed in version 26.8.1