External risk intelligence

SurrealDB Capability Check Bypass via JavaScript

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-134292

SurrealDB is a multi-model database engine frequently deployed as an internet-facing backend service or API endpoint for web and mobile applications. As a database, it is often exposed to network-accessible application layers, making it a common target for external interface interaction, even if access control is required.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in SurrealDB's JavaScript engine allows authenticated users to bypass access controls and execute unauthorized built-in functions. This could enable attackers to gain unintended access or control over database operations. The primary concern is confirming if this technology is in use within the organization and, if so, assessing the potential exposure.

  • Unauthorized function execution bypasses controls.
  • Impacts systems using SurrealDB's scripting.
  • Confirm relevance and assess exposure.

Attack Path

How an attacker could exploit the issue

An attacker can leverage the SurrealDB JavaScript engine to bypass permission checks for built-in functions. This occurs when the `surrealdb.functions` bridge calls internal dispatchers without verifying user capabilities. Consequently, authenticated users who are normally restricted from using certain SurrealQL functions can execute them by invoking them through JavaScript.

  • Requires authenticated access.
  • Triggered via JavaScript `surrealdb.functions`.
  • Bypasses function access controls.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow authenticated users who are denied access to certain SurrealQL functions to execute them. This is possible by calling these functions through the `surrealdb.functions` bridge within embedded JavaScript, bypassing intended capability checks.

  • Functionality restricted to authorized users.
  • Bypass checks via embedded JavaScript.
  • Unauthorized function execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts SurrealDB, and its ownership typically falls to the application or platform team managing the database instance. The first critical step is to identify all deployments of the affected SurrealDB version, assess their exposure and business criticality, and then coordinate with the vendor for remediation.

  • Application or platform teams own the issue.
  • Verify SurrealDB deployment exposure and criticality.
  • Plan vendor-coordinated remediation.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is SurrealDB?

SurrealDB is a modern multi-model database engine. Developers use it to manage complex data structures for web and mobile applications, often deploying it as a backend service or API endpoint to handle storage, querying, and custom logic through its integrated JavaScript scripting engine.

What is the weakness in CVE-2026-134292?

This vulnerability is a Missing Authorization issue (CWE-862). It occurs because the software's JavaScript bridge fails to check user permissions before executing internal database functions. Essentially, the security gate that prevents restricted users from running sensitive commands is bypassed when those commands are called via JavaScript.

How can an attacker trigger this vulnerability?

An attacker needs an authenticated session to the database. They can then invoke built-in SurrealQL functions by calling them through the `surrealdb.functions` bridge in embedded JavaScript. Simply having access to the database interface does not trigger the bug; the attacker must specifically utilize the JavaScript engine to reach these internal dispatchers.

Is my environment at risk from this CVE?

Halo Surface Signal indicates that because SurrealDB is frequently deployed as an internet-facing backend, it is often exposed to external interaction. If your instance is reachable over a network—especially if it supports authenticated users—it is more likely to be a target for this type of capability bypass.

What should I do if I use SurrealDB?

Start by identifying all instances of SurrealDB version 1.0.0 through 3.x across your infrastructure. Determine which of these are reachable by users and assess the impact if an authenticated user could run unauthorized functions. Once identified, coordinate with your platform team to prepare for vendor-supplied updates.

References