# CVE-2026-93593: ArcadeDB before 26.9.1 TimeSeries ACL Bypass via Type Permission

> An authenticated low-privilege user can bypass ACL restrictions to read or insert TimeSeries data in ArcadeDB due to flawed permission resolution logic.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-46xr-4762-9x3m, GHSA-wjhv-79gv-2pqg

## What is CVE-2026-93593?

CVE-2026-93593 is a high-severity missing authorization vulnerability in ArcadeData arcadedb, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ArcadeDB before 26.9.1 fails to enforce security-group types ACL entries for TimeSeries types because the ACL resolver builds permissions from bucket IDs, but TimeSeries types do not own normal record buckets. An authenticated low-privilege user can read or insert TimeSeries samples despite explicit deny rules by exploiting the missing type-name-based access check that causes permission lookups to fail open.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-93593 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93593 is a high-severity missing authorization vulnerability in ArcadeData arcadedb, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93593 exists.

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-93593/ (Markdown: https://insights.sbomify.com/CVE-2026-93593/index.md)
```

## Sources

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

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