Skip to main content
Menu
CVEs

ArcadeData schema disclosure through per-type ACL bypass

Affects ArcadeDB arcadedb-engine 26.7.1 through 26.10.2, and grpcw, ha-raft and postgresw up to 26.10.2, where per-type permissions deny a type. Fixed in 26.11.1.

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

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

Summary

Written by a model

ArcadeDB before 26.11.1 contains an authorization bypass vulnerability that allows authenticated users to read schema definitions of denied types through listings ignoring per-type ACLs. Attackers can query the PostgreSQL wire catalog, GraphQL introspection, or MCP get_schema to reveal property names, indexes, inheritance, and materialized view SQL.

Who should check

Teams running ArcadeDB Maven packages (arcadedb-engine, arcadedb-grpcw, arcadedb-ha-raft, arcadedb-postgresw) before 26.11.1 that use per-type ACLs

“>= 26.7.1, <= 26.10.2”

github.com

What to do

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

    Affected ArcadeDB versions: arcadedb-engine >= 26.7.1 and <= 26.10.2; grpcw, ha-raft and postgresw <= 26.10.2 The user has database access but per-type permissions deny the type
  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-134327 (ArcadeDB before 26.11.1 Schema Information Disclosure via Per-Type ACL Bypass), 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-134327 (entry last updated 2026-11-21):
Affected:
- Maven package com.arcadedb:arcadedb-postgresw: fixed in 26.11.1
- Maven package com.arcadedb:arcadedb-grpcw: fixed in 26.11.1
- Maven package com.arcadedb:arcadedb-ha-raft: fixed in 26.11.1
- Maven package com.arcadedb:arcadedb-engine: from 26.7.1, fixed in 26.11.1
Fixed versions: 26.11.1.
Conditions (all must be true for the bug to be hit):
- Affected ArcadeDB versions: arcadedb-engine >= 26.7.1 and <= 26.10.2; grpcw, ha-raft and postgresw <= 26.10.2 (source: https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-vpxw-wqc5-hvvj)
- The user has database access but per-type permissions deny the type (source: https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-vpxw-wqc5-hvvj)
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-134327 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134327 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-vpxw-wqc5-hvvj
- https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-48q6-q453-cm77
- https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-4mmv-84cq-wpc5
- https://www.vulncheck.com/advisories/arcadedb-before-26.11.1-schema-information-disclosure-via-per-type-acl-bypass
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-134327
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-134327"}.

Affected versions

cve.now Index

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

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 32 if CISA's SSVC rates it automatable

Impact

Timeline

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

Evidence 6

Questions about CVE-2026-134327

Is CVE-2026-134327 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 with database access but per-type permissions that deny a type can still read that type's schema metadata, including property names, indexes, inheritance and materialized view SQL.

Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-134327?

com.arcadedb:arcadedb-postgresw (Maven): before 26.11.1. com.arcadedb:arcadedb-grpcw (Maven): before 26.11.1. com.arcadedb:arcadedb-ha-raft (Maven): before 26.11.1. com.arcadedb:arcadedb-engine (Maven): from 26.7.1 before 26.11.1.

Source: cve.now feed data

Am I affected, and how do I check?

The listed ranges are arcadedb-engine 26.7.1 through 26.10.2, and grpcw, ha-raft and postgresw up to 26.10.2. To check a setup, compare the installed ArcadeDB version against these ranges and see whether per-type permissions are used to deny access to any types.

Source: github.com, vulncheck.com

How do I fix CVE-2026-134327?

Upgrade to ArcadeDB 26.11.1 or later, which is the listed fixed version.

Source: github.com, vulncheck.com

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