Skip to main content
Menu
CVEs

ArcadeData ArcadeDB Server authorization bypass in batch API endpoint

Only affects arcadedb-server 26.11.1-SNAPSHOT builds before 26.11.1, where the first batch request to an on-disk database that is not yet open runs with no principal bound. Fixed in 26.11.1.

CVE-2026-134339Published November 21, 2026, updated

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 26.11.1
Who is exposed
Specific setups only

Summary

Written by a model

ArcadeDB from 26.11.1-SNAPSHOT before 26.11.1 contains an authorization bypass vulnerability that allows authenticated users to skip per-type ACL checks when a database is opened on demand. Attackers can send the first POST /api/v1/batch/{database} request to a closed database to read and write types they are not entitled to access.

Who should check

Teams running ArcadeDB server builds from 26.11.1-SNAPSHOT before 26.11.1 (Maven com.arcadedb:arcadedb-server), especially those with databaseLoadAtStartup=false and per-type ACLs.

Not fixed by: A second registry-membership test would reintroduce the same defect in a different place.

“>= 26.11.1-SNAPSHOT, < 26.11.1”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    Affected versions 26.11.1-SNAPSHOT up to but not including 26.11.1 (arcadedb-server Maven package). The target database is on disk and not yet open, so the first batch request opens it.
  2. Upgrade to a fixed version: 26.11.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134339 (ArcadeDB from 26.11.1-SNAPSHOT before 26.11.1 Authorization Bypass via Batch Endpoint), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134339 (entry last updated 2026-11-21):
Affected:
- Maven package com.arcadedb:arcadedb-server: from 26.11.1-SNAPSHOT, fixed in 26.11.1
Fixed versions: 26.11.1.
Conditions (all must be true for the bug to be hit):
- Affected versions 26.11.1-SNAPSHOT up to but not including 26.11.1 (arcadedb-server Maven package). (source: https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-97h7-j68g-w3r2)
- The target database is on disk and not yet open, so the first batch request opens it. (source: https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-97h7-j68g-w3r2)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134339 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134339 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Maven): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-97h7-j68g-w3r2
- https://www.vulncheck.com/advisories/arcadedb-from-26.11.1-snapshot-before-26.11.1-authorization-bypass-via-batch-endpoint
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134339
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134339"}.

Affected versions

cve.now Index

27Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects Maven packages
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 77 if added to CISA KEV
  • Would score about 72 if CISA's SSVC rates exploitation active
  • Would score about 34 if CISA's SSVC rates it automatable

Impact

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · ArcadeData/arcadedb · Advisory GHSA-97h7-j68g-w3r2
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134339
RecordNVD · CVE-2026-134339
Other links 1
Linkvulncheck.com · advisories/arcadedb-from-26.11.1-snapshot-before-26.11.1-authorization-bypass-via-batch-endpoint

Questions about CVE-2026-134339

Is CVE-2026-134339 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

An authenticated user with database access but restricted per-type permissions can read and write types they are not entitled to. The first batch request to an on-disk database that is not yet open runs with no principal bound, which skips the per-type checks.

Source: github.com

Which versions are affected by CVE-2026-134339?

com.arcadedb:arcadedb-server (Maven): from 26.11.1-SNAPSHOT before 26.11.1.

Source: cve.now feed data

Am I affected, and how do I check?

The arcadedb-server (Maven package) versions from 26.11.1-SNAPSHOT up to but not including 26.11.1 are affected. To check a deployment, look at the arcadedb-server version in use, and note whether the target database is on disk and not yet open when the first batch request arrives.

Source: github.com

How do I fix CVE-2026-134339?

Upgrade arcadedb-server to 26.11.1 or later, which is the fixed version.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.