External risk intelligence

ArcadeDB Missing Authentication in Redis Plugin Allows Data Access

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-75854

The vulnerability exists in a Redis wire-protocol plugin for a database. While database ports are typically restricted to internal network access or specific application server communication, Redis protocols are sometimes exposed to the internet in misconfigured deployments, making remote reachability possible but not the intended or standard deployment pattern.

Missing Authentication

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in the Redis wire-protocol plugin for ArcadeDB. This issue allows attackers to bypass authentication and gain unauthorized access to read, write, and delete data within any database on the server. This could significantly impact data integrity and confidentiality if exploited.

  • Unauthenticated database access is possible.
  • Protects against unauthorized data access and modification.
  • Confirm relevance and assess exposure.

Attack Path

How an attacker could exploit the issue

An attacker could target the Redis wire-protocol plugin to bypass authentication. By connecting to the Redis port, an attacker can issue commands to any database on the server without needing credentials. This direct access allows for unauthorized data manipulation.

  • Unauthenticated network access required.
  • Triggered by connecting to the Redis port.
  • Enables arbitrary data read, write, or delete.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow unauthenticated attackers to read, write, and delete data by connecting to the Redis port and executing arbitrary commands against any database on the server. This bypasses all security controls when the Redis wire-protocol plugin is enabled and accessible.

  • Database data and operations at risk.
  • Unauthenticated remote access to Redis port.
  • Unauthorized data manipulation and loss.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical vulnerability in ArcadeDB's Redis wire-protocol plugin requires immediate attention from teams responsible for database infrastructure and application security. The primary first step is to identify all instances of ArcadeDB, confirm their exposure to the network, and assess their business criticality. Once identified, the accountable owners must be located to coordinate remediation efforts, prioritizing systems with the greatest risk.

  • Database and security teams should own.
  • Verify Redis port exposure and reachability.
  • Plan and execute remediation actions.

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 ArcadeDB?

ArcadeDB is a multi-model database engine designed to handle various data formats, including graph, document, and relational models, within a single system. It supports multiple communication protocols, allowing it to interact with different tools and environments through specific plugins.

What does CWE-306 mean for CVE-2026-75854?

CWE-306 refers to a Missing Authentication for Critical Function weakness. In this case, the Redis wire-protocol plugin for ArcadeDB fails to verify a user's identity before granting access. This means the system treats any connection request as authorized, allowing outsiders to interact with the database as if they were a trusted user.

How does an attacker trigger this vulnerability?

An attacker triggers this by initiating a network connection directly to the Redis port enabled on an ArcadeDB server. The bug is specifically tied to the Redis plugin; if this plugin is disabled or the port is not reachable, the vulnerability cannot be triggered through this path.

Is my server at risk if it is not internet-facing?

According to Halo Surface Signal, this vulnerability is classified as external because it relies on network reachability. While the threat is most severe when exposed to the internet, it remains a concern if your internal network architecture allows unauthorized segments or compromised devices to communicate with the Redis port.

What should I do first to address this CVE?

Start by identifying all instances of ArcadeDB across your environment that have the Redis wire-protocol plugin enabled. Once you have a complete inventory, verify whether those ports are accessible from outside your trusted network boundaries and coordinate with your infrastructure team to apply the necessary updates.

References