ArcadeData ArcadeDB Engine denial of service via query cache timeout bypass
Affects ArcadeDB from 21.10.1 before 26.11.1 where user groups set readTimeout or resultSetLimit. The affected range ends before 26.11.1, which is the fixed version.
- Exploited
- No known exploitation
- Fix
- Fixed in 26.11.1
- Who is exposed
- Specific setups only
Summary
Written by a model
ArcadeDB 21.10.1 before 26.11.1 contains a resource-limit bypass vulnerability that allows restricted users to evade per-group readTimeout because limits are applied to shared cached statements and plans. Attackers can run SQL text previously cached by an unrestricted principal to skip timeouts, or impose their own timeout and limit on root and other users.
Who should check
Teams running ArcadeDB server 26.10.2 or earlier (from 21.10.1) that set per-group readTimeout or resultSetLimit for database users, including Maven users of com.arcadedb:arcadedb-engine
“readTimeout and resultSetLimit of a user's groups are applied by mutating the parsed Statement”
What to do
Check whether your setup matches what the bug needs.
Users' groups set readTimeout or resultSetLimit (server security profile applies per-group limits) Another principal ran the same SQL text first since the last schema changeUpgrade to a fixed version: 26.11.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134335 (ArcadeDB 21.10.1 before 26.11.1 readTimeout Bypass via Shared Statement and Plan Cache), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-134335 (entry last updated 2026-11-21):
Affected:
- Maven package com.arcadedb:arcadedb-engine: from 21.10.1, fixed in 26.11.1
Fixed versions: 26.11.1.
Conditions (all must be true for the bug to be hit):
- Users' groups set readTimeout or resultSetLimit (server security profile applies per-group limits) (source: https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-3wmm-4xjp-4h7q)
- Another principal ran the same SQL text first since the last schema change (source: https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-3wmm-4xjp-4h7q)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134335 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134335 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Maven): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-3wmm-4xjp-4h7q
- https://www.vulncheck.com/advisories/arcadedb-21.10.1-before-26.11.1-readtimeout-bypass-via-shared-statement-and-plan-cache
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-134335
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134335"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Maven packages
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 30 if CISA's SSVC rates it automatable
Impact
- Widely used18 packages depend on com.arcadedb:arcadedb-engine. deps.dev
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · ArcadeData/arcadedb · Advisory GHSA-3wmm-4xjp-4h7q |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134335 |
| Record | NVD · CVE-2026-134335 |
| Other links 1 | |
| Link | vulncheck.com · advisories/arcadedb-21.10.1-before-26.11.1-readtimeout-bypass-via-shared-statement-and-plan-cache |
Questions about CVE-2026-134335
Is CVE-2026-134335 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A restricted user can run queries without the readTimeout their group sets, which removes a denial-of-service guard. A restricted user can also impose a timeout or result limit on root and other users running the same SQL text, which degrades their queries.
Source: github.com
Which versions are affected by CVE-2026-134335?
com.arcadedb:arcadedb-engine (Maven): from 21.10.1 before 26.11.1.
Source: cve.now feed data
Am I affected, and how do I check?
The affected range is ArcadeDB 21.10.1 up to but not including 26.11.1. The issue involves user groups that set readTimeout or resultSetLimit, and it applies when another principal ran the same SQL text first since the last schema change. To check a version, look at the installed ArcadeDB release, and to check the setup, look at whether any group in the server security profile sets readTimeout or resultSetLimit.
Source: github.com
How do I fix CVE-2026-134335?
Upgrade to ArcadeDB 26.11.1 or later, the fixed version in the affected range. The facts do not list a workaround.
Source: github.com
Related
- CVE-2026-67341ArcadeDB before 26.7.2 Authorization Bypass via SQL DEFINE FUNCTION
- CVE-2026-67340ArcadeDB before 26.7.2 Remote Code Execution via Trigger Scripts
- CVE-2026-76225ArcadeDB before 26.8.1 Server-Side Request Forgery via LOAD CSV
- CVE-2026-75842ArcadeDB before 26.8.1 Arbitrary File Read via LOAD CSV
- CVE-2026-54076ArcadeDB: Read-only users can mutate database schema (incomplete fix of CVE-2026-44221)
- CVE-2026-134327ArcadeDB before 26.11.1 Schema Information Disclosure via Per-Type ACL Bypass
No corrections so far. Something wrong on this page? Report an error.