# CVE-2026-67356: ArcadeDB before 26.7.3 Privilege Escalation via JavaScript Trigger

> Attackers with schema-admin permissions can escalate privileges to server-wide admin by creating JavaScript triggers that bypass security checks.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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:** 2 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-38pf-6hp2-pxww, GHSA-p28w-g8xf-vm54

## What is CVE-2026-67356?

CVE-2026-67356 is a high-severity vulnerability in ArcadeData arcadedb, published on 2 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ArcadeDB before 26.7.3 binds the real LocalDatabase object into JavaScript trigger contexts with HostAccess.ALL, allowing schema-admins to call getSecurity().createUser() without permission checks. Attackers with UPDATE_SCHEMA permission can create triggers that execute JavaScript to create server-wide admin users, escalating privileges beyond their authorization level.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-67356 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67356 is a high-severity vulnerability in ArcadeData arcadedb, published on 2 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-67356 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-67356/ (Markdown: https://insights.sbomify.com/CVE-2026-67356/index.md)
```

## Sources

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

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