CVE-2026-44221: CWE-863: Incorrect Authorization in ArcadeData arcadedb
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.
AI Analysis
Technical Summary
ArcadeDB versions before 2.6.4 contain an incorrect authorization vulnerability (CWE-863) where authenticated principals scoped to one database could read, write, and mutate schemas on other databases on the same server. This arises from ServerSecurityUser.getDatabaseUser() returning a user with an uninitialized fileAccessMap treated as allow-all by requestAccessOnFile, and from ArcadeDBServer.createDatabase() failing to set security on newly created databases via the API, effectively disabling record-level authorization. These combined defects enable bypass of authorization mechanisms. The issue is addressed in ArcadeDB 2.6.4.
Potential Impact
The vulnerability allows authenticated users or API tokens with access to one database to escalate privileges and access or modify other databases on the same server, including schema changes. This can lead to unauthorized data disclosure, data modification, and potential denial of service. The CVSS 3.1 score is 9.0 (critical), reflecting network attack vector, low attack complexity, required privileges, user interaction, and high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
A fix is available in ArcadeDB version 2.6.4. Users should upgrade to this version or later to remediate the vulnerability. No official temporary workaround or alternative mitigation is indicated in the provided data. Patch status is confirmed by the vendor's versioning information.
CVE-2026-44221: CWE-863: Incorrect Authorization in ArcadeData arcadedb
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
ArcadeDB versions before 2.6.4 contain an incorrect authorization vulnerability (CWE-863) where authenticated principals scoped to one database could read, write, and mutate schemas on other databases on the same server. This arises from ServerSecurityUser.getDatabaseUser() returning a user with an uninitialized fileAccessMap treated as allow-all by requestAccessOnFile, and from ArcadeDBServer.createDatabase() failing to set security on newly created databases via the API, effectively disabling record-level authorization. These combined defects enable bypass of authorization mechanisms. The issue is addressed in ArcadeDB 2.6.4.
Potential Impact
The vulnerability allows authenticated users or API tokens with access to one database to escalate privileges and access or modify other databases on the same server, including schema changes. This can lead to unauthorized data disclosure, data modification, and potential denial of service. The CVSS 3.1 score is 9.0 (critical), reflecting network attack vector, low attack complexity, required privileges, user interaction, and high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
A fix is available in ArcadeDB version 2.6.4. Users should upgrade to this version or later to remediate the vulnerability. No official temporary workaround or alternative mitigation is indicated in the provided data. Patch status is confirmed by the vendor's versioning information.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-05T15:42:40.518Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a038bd7cbff5d8610164960
Added to database: 5/12/2026, 8:21:43 PM
Last enriched: 5/12/2026, 8:36:54 PM
Last updated: 5/13/2026, 4:59:56 AM
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.