LiveActive security incident?Get immediate response
CVE Record

CVE-2026-75851: ArcadeDB before 26.8.1 Authentication Bypass via Async Command

ArcadeDB server (com.arcadedb:arcadedb-server) in versions 26.7.3 and earlier fails to propagate the authenticated principal to asynchronous command worker threads. When an HTTP command is submitted with awaitResponse:false, it executes on an async worker whose DatabaseContext has no bound user, causing the scripting authorization gate to become a no-op. A user with only read access to a single database can submit an asynchronous JavaScript (language=js) command via the /api/v1/command endpoint to run code with unrestricted host access (e.g., database.getSecurity().createUser) and create a server-wide administrator, escalating to full administrative control. Fixed in 26.8.1.

CriticalCVSS 9.9Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A low-privileged ArcadeDB user can bypass authorization through asynchronous JavaScript commands and potentially create a server-wide administrator. Successful abuse could expose, alter, or disrupt every database managed by the server. ArcadeDB 26.8.1 fixes the flaw.

Executive priority

Treat as an immediate remediation priority. The vulnerability crosses a database security boundary and can convert minimal legitimate access into complete administrative control. Upgrade exposed systems first, restrict access during remediation, and investigate vulnerable servers for unauthorized administrator creation.

Technical view

ArcadeDB 26.7.3 and earlier do not propagate the authenticated principal to asynchronous command workers. With awaitResponse:false, the worker DatabaseContext lacks a bound user, making the scripting authorization gate ineffective. A read-only database user can consequently execute JavaScript with unrestricted host access and escalate privileges. This is classified as CWE-269 with CVSS 3.1 score 9.9.

Likely exposure

Exposure requires a vulnerable ArcadeDB server, access to the HTTP command endpoint, and valid credentials with at least read access to one database. Internet or broadly network-accessible deployments and widely issued low-privilege accounts face greater practical risk. The supplied sources do not quantify exposed installations.

Exploitation context

The described path is remotely reachable and requires low privileges, low complexity, and no user interaction. The source bundle reports that this CVE is not in KEV and provides no evidence of active exploitation. It does establish a credible route to server-wide administrative control.

Researcher notes

The core defect is missing security-context propagation across an asynchronous execution boundary, not credential-free authentication bypass. The authorization decision becomes ineffective because the worker has no bound principal. Assessment should focus on version, command-endpoint reachability, low-privilege account access, asynchronous JavaScript activity, and unexpected server-wide principals.

Mitigation direction

  • Upgrade ArcadeDB server to version 26.8.1 or later.
  • Prioritize externally reachable or broadly accessible ArcadeDB deployments.
  • Restrict network access to the command API until upgrading is complete.
  • Review server-wide administrators and revoke any unauthorized accounts.
  • Consult the vendor advisory for deployment-specific guidance.

Validation and detection

  • Inventory ArcadeDB server versions and identify installations running 26.7.3 or earlier.
  • Confirm upgraded servers report version 26.8.1 or later.
  • Identify which users can reach the HTTP command endpoint.
  • Review server-wide administrator accounts for unexpected additions.
  • If telemetry exists, investigate asynchronous JavaScript command activity.
  • Validate authorization for asynchronous commands in a controlled, non-production environment.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-269: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-75851 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.9CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16VulnCheck
9.4CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

9.4Critical
CVSS 4.0 vector shape for CVE-2026-75851Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ArcadeDataarcadedb0, 26.8.1unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-269 · source CWE mapping

Improper Privilege Management

Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.