Skip to main content
VulnerabilityPublished Updated

CVE-2026-76224: ArcadeData arcadedb · Code Injection

Affects ArcadeData arcadedbSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 26.8.1 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 26.8.1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade arcadedb and arcadedata/arcadedb to 26.8.1.

Affected software

ProductAffectedFixed in
ArcadeDataarcadedbAffected
  • <26.8.1
Fixed in
  • 26.8.1
GitHubarcadedata/arcadedbpkg:github/arcadedata/arcadedbOther threatsAffected
  • <26.8.1
Fixed in
  • 26.8.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in ArcadeDB version 26.8.1. Users should upgrade to version 26.8.1 or later to remediate this vulnerability. No vendor advisory content was provided, but the version information indicates an official fix exists. Until upgraded, restrict access to authenticated users and monitor for suspicious query activity.

Description

ArcadeDB versions before 26.8.1 contain a remote code execution vulnerability in the Gremlin query engine. The vulnerability arises because the ArcadeGremlin.executeStatement() method falls back to an insecure Groovy engine when a query with parameters does not parse as gremlin-lang. This fallback allows an authenticated user with any database role, including read-only, to execute arbitrary operating system commands as the server process user.

References

Community reviews

Loading reviews…