Security readout for executives and security teams
Plain-English summary
ArcadeDB versions 21.10.1 through before 26.4.2 can let an authenticated user or scoped API token access other databases on the same server. Newly created databases may also have record-level authorization disabled. For shared ArcadeDB servers, this can undermine tenant or application separation and expose sensitive data or schema integrity.
Executive priority
Treat as urgent for any multi-database ArcadeDB deployment. The flaw can defeat intended access boundaries for authenticated users, creating material data exposure and integrity risk. Prioritize upgrade and post-upgrade access review.
Technical view
The advisory describes a CWE-863 authorization bypass. ServerSecurityUser.getDatabaseUser() returned a database user with an uninitialized fileAccessMap, causing requestAccessOnFile to allow access broadly. Separately, createDatabase() omitted factory.setSecurity(...), leaving record-level authorization disabled for databases created through the server API. Fixed in ArcadeDB 26.4.2.
Likely exposure
Organizations running ArcadeDB >=21.10.1 and <26.4.2 are potentially exposed, especially where multiple databases share one server or scoped API tokens are used for isolation.
Exploitation context
Sources state exploitation requires an authenticated principal or API token. KEV is false and the provided sources do not report active exploitation. Impact is high because confidentiality, integrity, and availability across databases can be affected.
Researcher notes
The issue is source-grounded in the GitHub advisory and two commits. Public details identify root causes and the fixed version, but no KEV listing or cited active exploitation evidence is provided in the bundle.
Mitigation direction
- Upgrade ArcadeDB to version 26.4.2 or later.
- Review vendor advisory and commits for deployment-specific remediation guidance.
- Rotate or review scoped API tokens after upgrade where cross-database exposure was possible.
- Assess databases created during affected versions for authorization configuration issues.
Validation and detection
- Inventory ArcadeDB server versions and identify any below 26.4.2.
- Confirm whether multiple databases share the same ArcadeDB server.
- Review access logs for scoped users accessing unexpected databases.
- Verify record-level authorization is enabled on databases created during affected versions.
- Confirm upgraded systems include the referenced security fixes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-44221 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H2.36GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-fxc7-fm93-6q77CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/ArcadeData/arcadedb/commit/04110c06315da55604ac107f71fe7182f3a3deb8CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/ArcadeData/arcadedb/commit/9e708f116bCVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.