Authorization Flaw in com.arcadedb:arcadedb-server (CVE-2026-44221)
Summary
Vulnerability in com.arcadedb:arcadedb-server (CVE-2026-44221). Successful exploitation can lead to full system takeover. Exploitable via POST /api/v1/server. Mitigation: upgrade to 26.4.2 or later.
Original description
The description as published by the source.
ArcadeDB is a Multi-Model DBMS. Starting in version 21.10.1 and prior to version 26.4.2, 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 26.4.2.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44221 has been found in com.arcadedb:arcadedb-server.
Attackers can target a specific entry point like POST /api/v1/server over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.0/10.
What to do: upgrade com.arcadedb:arcadedb-server to 26.4.2 or later.
If unsure, ask your IT team or search "com.arcadedb:arcadedb-server CVE-2026-44221" on the vendor's site.
CVE-2026-44221 (com.arcadedb:arcadedb-server) — CWE-863 / CVSS v3 9.0
Attack vector: remote (network-reachable)
Attack surface: POST /api/v1/server
Patched: 26.4.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Incorrect authorization (CWE-863) exists in com.arcadedb:arcadedb-server. Attackers reach the vulnerable code path via POST /api/v1/server.
Check the vendor advisory for the affected versions of com.arcadedb:arcadedb-server. Attack surface: POST /api/v1/server.
Severity: Critical (CVSS 9.0/10). Successful exploitation can lead to full system takeover.
Update to 26.4.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/v1/server requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで com.arcadedb:arcadedb-server を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'POST /api/v1/server' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/v1/serverへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade com.arcadedb:arcadedb-server to 26.4.2ステージング環境で 26.4.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/v1/server on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com