# CVE-2026-75846: ArcadeDB before 26.8.1 Unauthorized Function Deletion via DELETE FUNCTION


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-v5p2-j769-79j6, GHSA-vv82-qvpf-rjwv

## What is CVE-2026-75846?

CVE-2026-75846 is a high-severity vulnerability in ArcadeData arcadedb, published on 18 Aug 2026. 

### Official description

ArcadeDB before 26.8.1 (affected versions <= 26.7.3) contains a missing authorization vulnerability in the DELETE FUNCTION SQL statement. DeleteFunctionStatement.executeSimple unregisters and persists deletion of a server-side function without any checkPermissionsOnDatabase (UPDATE_SCHEMA) check. Any user with database access can execute DELETE FUNCTION via the command API (POST /api/v1/command/{db}) to permanently remove any registered server-side function, including security-relevant logic, impacting integrity and availability.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-75846 being exploited?

There is no known exploitation of CVE-2026-75846 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75846 is a high-severity vulnerability in ArcadeData arcadedb, published on 18 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-75846 in the wild and no public exploit code.

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

## Sources

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

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