CVE-2026-114056: ArcadeDB authorization bypass in ALTER TYPE edge schema

CVE-2026-114056 · Severity: medium · CVSS 4.3 · Published 2026-10-21

ArcadeDB is a graph database engine. A read-only user can bypass authorization controls and permanently modify edge type storage flags (lightweight and unique declarations) by sending a specially crafted SQL command, even though they lack the UPDATE_SCHEMA permission required for schema changes. This violates the documented permission model and could affect application behavior that depends on the declared storage format.

Technologies: ArcadeData ArcadeDB. Vendors: ArcadeData.

Quick answers

Is CVE-2026-114056 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-114056 being exploited in the wild.
How severe is CVE-2026-114056?
Medium severity, with a CVSS score of 4.3, published 21 October 2026.
Which products and versions are affected?
ArcadeData ArcadeDB 26.8.1 through 26.9.1.
Is there a fix for CVE-2026-114056?
Yes: fixed in 26.10.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-114056 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-114056?
Check whether you run ArcadeData ArcadeDB at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 26.10.1

Technical details

The vulnerability is an authorization bypass (CWE-862) in the ALTER TYPE statement parser. The edge-type setters setLightweight() and setUnique() in LocalEdgeType lack the checkForSchemaMutation() call that enforces UPDATE_SCHEMA permission. When ALTER TYPE is issued with only a WITH clause (no ALTER items), the per-item authorization loop is skipped and the unguarded setters are called directly, allowing a read-only authenticated user to persist schema changes. An attacker needs only a valid read-only database credential and network access to the HTTP, gRPC, or Bolt command API (enabled by default).

Affected products

  • ArcadeData ArcadeDB 26.8.1 through 26.9.1

Timeline

  • 2026-10-05: disclosed
  • 2026-10-21: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.