# CVE-2026-76224: ArcadeDB before 26.8.1 Remote Code Execution via Groovy Fallback

> Authenticated users can execute arbitrary OS commands via Groovy fallback in ArcadeDB's Gremlin engine, requiring an upgrade to secure versions.

- **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:** 19 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-qf82-gwmv-gc98, GHSA-wcm5-4wjm-9wj3

## What is CVE-2026-76224?

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

### Official description

ArcadeDB before 26.8.1 (arcadedb-gremlin, affected <= 26.7.3) contains a remote code execution vulnerability in its Gremlin query engine. Although the engine defaults to the documented-secure java (gremlin-lang) engine, ArcadeGremlin.executeStatement() silently falls back to the insecure Groovy engine whenever a request carries any query parameter and the query does not parse as gremlin-lang. An authenticated user with any database role, including a read-only reader, can submit a parameterized Gremlin query to trigger the Groovy fallback and execute arbitrary operating system commands as the ArcadeDB server process user.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2026-76224 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76224 is a high-severity code injection vulnerability in ArcadeData arcadedb, published on 19 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-76224 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-76224/ (Markdown: https://insights.sbomify.com/CVE-2026-76224/index.md)
```

## Sources

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

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