Open-source package vulnerability · Maven

CVE-2026-44221: ArcadeDB vulnerable to cross-database authorization bypass and unsecured newly-created databases

criticalCVSS 3.1 9.0GHSA-fxc7-fm93-6q77

Impact 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;

Published May 5, 2026 · Updated Aug 3, 2026

Affected packages

com.arcadedb:arcadedb-server

Ecosystem: Maven
Affected: >= 21.10.1, < 26.4.2
Fixed in: 26.4.2
Check: mvn dependency:tree -Dincludes=com.arcadedb:arcadedb-server

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

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.

Patches

Upgrade to version 26.4.2

Resources

https://github.com/ArcadeData/arcadedb/commit/04110c06315da55604ac107f71fe7182f3a3deb8

Credited to sealbenb.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology