Vulnerability Description
ArcadeDB is a Multi-Model DBMS. Prior to 2.6.4, 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 2.6.4.
CVSS Score
CRITICAL
Related Weaknesses (CWE)
References
- https://github.com/ArcadeData/arcadedb/commit/04110c06315da55604ac107f71fe7182f3
- https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-fxc7-fm93-6q77
FAQ
What is CVE-2026-44221?
CVE-2026-44221 is a vulnerability with a CVSS score of 9.0 (CRITICAL). ArcadeDB is a Multi-Model DBMS. Prior to 2.6.4, 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 dist...
How severe is CVE-2026-44221?
CVE-2026-44221 has been rated CRITICAL with a CVSS base score of 9.0/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2026-44221?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.