CVE-2026-134337

ArcadeDB native builds could classify nested writes as read-only

ArcadeData · ArcadeDB native-image server · read-only query and MCP paths

First documented disclosure · Review checkpoint

Summary

Native-image query inspection could miss nested writes and admit them through read-only entry points.

Severity and exploitation evidence

High · 8.7/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

Missing reflection metadata left the SQL AST field cache empty, so nested statements and PROFILE-wrapped writes were not traversed.

Conditions required

A native-image server exposes a query interface to an authenticated user. Demonstrations used root; non-admin record-ACL bypass was not established.

Potential impact

Database mutation through a nominally read-only query path. MCP/HA reachability was identified statically rather than reproduced end to end.

Affected versions and configurations

Native-image builds 26.8.1 before 26.11.1. JVM controls rejected the same requests.

Fix and mitigation status

26.11.1 stable. Tagged code fails closed when AST reflection is unavailable and the native metadata includes parser fields.

Practical next steps

Upgrade native deployments to 26.11.1; use a corrected JVM deployment or disable the affected query surfaces until upgraded.

Operating lesson

Missing runtime metadata must cause authorization analysis to fail closed.

Evidence and limits

November 4 original and explicitly grouped PROFILE addendum; November 21 CNA ingestion. VulnCheck assigns CVSS 4.0 8.7 and 3.1 8.8; the maintainer labels the primary issue Moderate. The addendum’s vulnerable 26.11.1-SNAPSHOT was an October 21 build, not the November 4 stable release. Static review verified the AST-availability guard and 220 parser reflection entries; no local exploit or native build was executed.

Sources