CVE-2026-134327

ArcadeDB MCP schema listings exposed metadata for denied types

ArcadeData · ArcadeDB · MCP get_schema and grouped authorization paths

First documented disclosure · Review checkpoint

Summary

Authenticated users could enumerate schema metadata for types they could not read.

Severity and exploitation evidence

High · 7.1/10 · CVSS 4.0. Severity source.

Exploitation not established: The reviewed sources document a weakness or controlled demonstration; malicious exploitation against users is not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

Schema renderers did not filter per-type access; the issuer groups related cluster-alert, gRPC count and full-text statistics leaks under the same CVE.

Conditions required

A permitted interface and account can request metadata while being denied access to particular types or buckets.

Potential impact

Exposure of type names, properties, indexes, inheritance and view SQL. Grouped paths disclose counts or term frequencies; they do not directly return hidden record contents.

Affected versions and configurations

Engine: 26.7.1 before 26.11.1; other affected packages are listed by the CNA from 0 before 26.11.1. Original advisories list through 26.10.2.

Fix and mitigation status

26.11.1; the release lists authorization corrections, and tagged MCP schema rendering filters readable types.

Practical next steps

Upgrade to 26.11.1 and restrict metadata interfaces to users who need them.

Operating lesson

Schema and aggregate metadata require authorization independently of record access.

Evidence and limits

November 4 originals; November 21 CNA ingestion. VulnCheck CVSS 4.0 7.1 / 3.1 6.5 differs from the primary maintainer Moderate label and Low labels on some grouped paths. Primary tests invoked renderers directly rather than complete protocol sockets. Cluster/gRPC observations were static; the gRPC follow-up narrows the count claim to TimeSeries samples. The BM25 companion explicitly links to the primary advisory despite its own No known CVE field; it also reports restricted-user search failures after open. All four complete originals were reviewed; their mapping is explicit, not inferred from similarity.

Sources