# CVE-2026-114056: ArcadeDB from 26.8.1 before 26.10.1 Authorization Bypass via ALTER TYPE WITH


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-7762-mmrx-x9p5, GHSA-9c7g-grf7-j2r5

## What is CVE-2026-114056?

CVE-2026-114056 is a medium-severity vulnerability in ArcadeData arcadedb, published on 21 Oct 2026. 

### Official description

ArcadeDB from 26.8.1 before 26.10.1 contains an authorization bypass vulnerability that allows read-only users to modify edge type lightweight and unique schema flags without UPDATE_SCHEMA permission. Attackers can send a bare ALTER TYPE edgeType WITH lightweight = true command over the HTTP, gRPC, or Bolt command API to persistently alter edge storage declarations.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-114056?


## How do I fix CVE-2026-114056?

No fix has been published for CVE-2026-114056 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-114056 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114056 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114056 and fix it if it is affected.

What it is: CVE-2026-114056 is a medium-severity vulnerability in ArcadeData arcadedb, published on 21 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114056 exists.

Affected product: ArcadeData arcadedb. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-114056/ (Markdown: https://insights.sbomify.com/CVE-2026-114056/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-114056
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-114056
- OSV: https://osv.dev/vulnerability/CVE-2026-114056

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-114056/
Summaries are generated and may contain mistakes; the official description above is the record.