# CVE-2026-67344: ArcadeDB before 26.7.2 Authentication Bypass via ALTER TYPE

> Authenticated users with read-only access can bypass schema update permissions to modify database type metadata and routing strategies.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-8vr5-263f-x5r3, GHSA-qwhj-f36r-39x7

## What is CVE-2026-67344?

CVE-2026-67344 is a high-severity missing authorization vulnerability in ArcadeData arcadedb, published on 1 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ArcadeDB before 26.7.2 fails to enforce the UPDATE_SCHEMA database permission on the ALTER TYPE ... CUSTOM and ALTER TYPE ... BUCKETSELECTIONSTRATEGY SQL operations, which map to setCustomValue and setBucketSelectionStrategy in LocalDocumentType. An authenticated user with only read access (e.g., a read-only API token) can submit these ALTER TYPE statements via the HTTP command endpoint to mutate a type's custom schema metadata and bucket-selection strategy, bypassing the documented updateSchema permission boundary and potentially corrupting schema metadata and record routing.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-67344 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67344 is a high-severity missing authorization vulnerability in ArcadeData arcadedb, published on 1 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67344 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-67344/ (Markdown: https://insights.sbomify.com/CVE-2026-67344/index.md)
```

## Sources

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

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