Information Disclosure in com.arcadedb:arcadedb-server (CVE-2026-67342)
Summary
Vulnerability in com.arcadedb:arcadedb-server (CVE-2026-67342). Successful exploitation can lead to full system takeover. Exploitable via POST /api/v1/batch/b. Mitigation: upgrade to 26.7.2 or later.
Original description
The description as published by the source.
ArcadeDB versions before 26.7.2 contain an authorization bypass vulnerability in HTTP handlers for time series, batch, Prometheus, and Grafana endpoints that fail to validate database access permissions. Attackers can access and modify databases they are not authorized to use by directly calling affected endpoints with arbitrary database parameters.
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-67342 has been found in com.arcadedb:arcadedb-server.
Attackers can target a specific entry point like POST /api/v1/batch/b over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade com.arcadedb:arcadedb-server to 26.7.2 or later.
If unsure, ask your IT team or search "com.arcadedb:arcadedb-server CVE-2026-67342" on the vendor's site.
CVE-2026-67342 (com.arcadedb:arcadedb-server) — CWE-200 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/v1/batch/b / POST /api/v1/ts/b/write / GET /api/v1/ts/b/prom/api/v1/query / POST /api/v1/ts/b/query
Patched: 26.7.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.
Information disclosure (CWE-200) exists in com.arcadedb:arcadedb-server. Attackers reach the vulnerable code path via POST /api/v1/batch/b without authentication.
Check the vendor advisory for the affected versions of com.arcadedb:arcadedb-server. Attack surface: POST /api/v1/batch/b / POST /api/v1/ts/b/write / GET /api/v1/ts/b/prom/api/v1/query / POST /api/v1/ts/b/query.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 26.7.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/batch/b 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/batch/b' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/v1/batch/bへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade com.arcadedb:arcadedb-server to 26.7.2ステージング環境で 26.7.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/v1/batch/b on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com