ArcadeData ArcadeDB Server authorization bypass in per-type ACLs via type rename
- Exploited
- No known exploitation
- Fix
- Fixed in 26.11.1
- Who is exposed
- Specific setups only
Summary
ArcadeDB 25.8.1 before 26.11.1 contains an incorrect authorization vulnerability because per-type ACLs are keyed by type name, renames are not propagated to the permission configuration, and requestAccessOnType allows unknown type names by default. Authenticated users holding only updateSchema can run ALTER TYPE NAME on a denied type to gain read, DELETE and TRUNCATE access, immediately for TIMESERIES types and after the next security rebuild for record-backed types.
Who should check
Teams running ArcadeDB server (Maven com.arcadedb:arcadedb-server) 25.8.1 to 26.10.2 that grant updateSchema or use per-type ACLs
“ArcadeDB 25.8.1 before 26.11.1 contains an incorrect authorization vulnerability”
What to do
Check whether your setup matches what the bug needs.
The attacker holds only the updateSchema privilege on a database and is explicitly denied access to a per-type ACL on the type being renamed Record-backed types become open only after the next security rebuild, which CREATE TYPE, DROP TYPE or index creation triggers; TIMESERIES types are open immediatelyUpgrade 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-134338 (ArcadeDB 25.8.1 before 26.11.1 Per-Type ACL Bypass via ALTER TYPE Rename), 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-134338 (entry last updated 2026-11-21):
Affected:
- Maven package com.arcadedb:arcadedb-server: from 25.8.1, fixed in 26.11.1
Fixed versions: 26.11.1.
Conditions (all must be true for the bug to be hit):
- The attacker holds only the updateSchema privilege on a database and is explicitly denied access to a per-type ACL on the type being renamed (source: https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-6pgq-xpqq-rmjx)
- Record-backed types become open only after the next security rebuild, which CREATE TYPE, DROP TYPE or index creation triggers; TIMESERIES types are open immediately (source: https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-6pgq-xpqq-rmjx)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134338 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134338 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-6pgq-xpqq-rmjx
- https://www.vulncheck.com/advisories/arcadedb-25.8.1-before-26.11.1-per-type-acl-bypass-via-alter-type-rename
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-134338
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-134338"}.Affected versions
cve.now Index
- 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
- Widely used12 packages depend on com.arcadedb:arcadedb-server. deps.dev
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · ArcadeData/arcadedb · Advisory GHSA-6pgq-xpqq-rmjx |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134338 |
| Record | NVD · CVE-2026-134338 |
| Other links 1 | |
| Link | vulncheck.com · advisories/arcadedb-25.8.1-before-26.11.1-per-type-acl-bypass-via-alter-type-rename |
Questions about CVE-2026-134338
Is CVE-2026-134338 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?
A user who holds only the updateSchema privilege on a database and is explicitly denied access to a per-type ACL on a type can rename that type to bypass the denial. After the rename they can read, DELETE and TRUNCATE the type.
Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-134338?
com.arcadedb:arcadedb-server (Maven): from 25.8.1 before 26.11.1.
Source: cve.now feed data
Am I affected, and how do I check?
ArcadeDB 25.8.1 up to but before 26.11.1 is affected. The bypass needs the updateSchema privilege plus an explicit per-type ACL denial on the renamed type; for record-backed types the access opens only after the next security rebuild, which CREATE TYPE, DROP TYPE or index creation triggers, while TIMESERIES types are open immediately. To check a version, look at the ArcadeDB server version reported in its startup output or admin interface.
Source: github.com, vulncheck.com
How do I fix CVE-2026-134338?
Upgrade ArcadeDB to 26.11.1 or later, which is the fixed version named in the advisory.
Source: github.com, vulncheck.com
Related
- CVE-2026-75851ArcadeDB before 26.8.1 Authentication Bypass via Async Command
- CVE-2026-67342ArcadeDB before 26.7.2 Authorization Bypass via Database Handlers
- CVE-2026-44221ArcadeDB: Cross-database authorization bypass and unsecured newly-created databases
- CVE-2026-134339ArcadeDB from 26.11.1-SNAPSHOT before 26.11.1 Authorization Bypass via Batch Endpoint
- CVE-2026-67343ArcadeDB before 26.7.2 Cluster Token Disclosure via GET /api/v1/server
- CVE-2026-93593ArcadeDB before 26.9.1 TimeSeries ACL Bypass via Type Permission
No corrections so far. Something wrong on this page? Report an error.