Answer in brief
CVE-2026-44221 records a Critical severity (CVSS 9.0) secret exfiltration vulnerability in ArcadeDB vulnerable to cross-database authorization bypass and unsecured newly-created databases. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
Answer in brief
CVE-2026-44221 records a Critical severity (CVSS 9.0) secret exfiltration vulnerability in ArcadeDB vulnerable to cross-database authorization bypass and unsecured newly-created databases. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
Update com.arcadedb:arcadedb-server to 26.4.2 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanSecret Exfiltration describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-44221 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| com.arcadedb:arcadedb-servermaven | >=21.10.1,<26.4.2 | 26.4.2 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-44221 records a Critical severity (CVSS 9.0) secret exfiltration vulnerability in ArcadeDB vulnerable to cross-database authorization bypass and unsecured newly-created databases. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for com.arcadedb:arcadedb-server.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate com.arcadedb:arcadedb-server to 26.4.2 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanSecret Exfiltration describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-44221 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| com.arcadedb:arcadedb-servermaven | >=21.10.1,<26.4.2 | 26.4.2 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-44221 records a Critical severity (CVSS 9.0) secret exfiltration vulnerability in ArcadeDB vulnerable to cross-database authorization bypass and unsecured newly-created databases. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for com.arcadedb:arcadedb-server.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard### 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
### 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