Skip to main content
VulnerabilityPublished Updated

CVE-2026-44221: ArcadeData arcadedb · Incorrect Authorization

Affects ArcadeData arcadedbSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.0 Critical : upgrade to 26.4.2 as a priority.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
9.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 26.4.2, 2.6.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 May 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 30 Oct 2026.

What to do

Upgrade arcadedb to 26.4.2; arcadedata/arcadedb to 2.6.4.

Affected software

ProductAffectedFixed in
ArcadeDataarcadedbAffected
  • >=21.10.1 <26.4.2
Fixed in
  • 26.4.2
GitHubarcadedata/arcadedbpkg:github/arcadedata/arcadedbOther threatsAffected
  • <2.6.4
Fixed in
  • 2.6.4

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

AI-suggested

Upgrade arcadedb to version 2.6.4 or later, where this vulnerability is fixed. The vendor has released an official patch addressing the uninitialized fileAccessMap and ensuring security settings are properly applied when creating databases via the API. No alternative mitigations are indicated. Patch status is confirmed by the vendor advisory and commit reference.

Description

ArcadeDB is a Multi-Model DBMS. Starting in version 21.10.1 and prior to version 26.4.2, authenticated users and API tokens scoped to a specific database could read, write, and mutate schema on any other database on the same server. Two distinct defects contributed: (1) ServerSecurityUser.getDatabaseUser() returned a DB user with an uninitialized fileAccessMap, which requestAccessOnFile treated as allow-all; (2) ArcadeDBServer.createDatabase() omitted factory.setSecurity(...) so any database created via POST /api/v1/server {"command":"create database X"} had its entire record-level authorization system silently disabled. In combination, record-level and database-level authorization could be bypassed by any authenticated principal. This vulnerability is fixed in 26.4.2.

References

Community reviews

Loading reviews…