/

CVE-2026-75852

Severity:

CRITICAL RISK

(9.8)

Missing Authentication (CWE-306) in ArcadeDB MongoDB

CVE-2026-75852

Deferred

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Unauthenticated Database Access and Modification

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

ArcadeDB's MongoDB wire-protocol plugin does not consistently enforce SASL authentication for data commands. An unauthenticated attacker who can connect to the MongoDB listener may read, create, modify, or delete data in any database, making this a critical access-control vulnerability.

Affected context

The vulnerability occurs in ArcadeDB deployments that expose the MongoDB wire-protocol plugin on port 27017 while relying on SASL authentication to protect database commands. It becomes risky when the listener is reachable by an attacker and command authorization is not enforced before data operations are processed.

Exploit preconditions

  • Attack surface: ArcadeDB's MongoDB wire-protocol listener, commonly exposed on port 27017
  • Required access: Network connectivity to the listener; valid credentials are not required
  • Trigger point: Issuing MongoDB data or database-management commands through the wire protocol
  • Why exploitation is possible: The plugin permits sensitive commands without first requiring successful SASL authentication

Why this happens

The underlying bug is an authentication enforcement failure in the MongoDB wire-protocol command handling path. Sensitive operations such as inserts, queries, updates, deletes, and database creation can be processed without verifying an authenticated session, mapping to CWE-306: Missing Authentication for Critical Function. The insecure pattern is allowing command execution based on network reachability rather than a completed authentication and authorization decision.

Potential impact

  • An attacker may read data from any accessible database
  • An attacker could insert or alter records
  • An attacker may delete data or disrupt database availability
  • An attacker could create databases or other persistent content
  • Compromised data could support fraud, information disclosure, or further attacks

General mitigation guidance

Mitigation generally focuses on making authentication and authorization mandatory for every sensitive protocol command.

Common defensive patterns include:

  • Enforcing successful SASL authentication before processing any data or database-management operation
  • Applying command-level authorization after authentication rather than treating login as sufficient
  • Binding the MongoDB listener to trusted network interfaces and limiting access with network policies or firewalls
  • Disabling unused protocol plugins and avoiding public exposure of database listeners
  • Using least-privilege database accounts and separating administrative permissions from routine data access
  • Monitoring and protecting configuration settings that control authentication enforcement

How teams detect issues like this

Organizations can look for this issue through:

  • Integration tests that attempt sensitive commands before authentication and verify consistent rejection
  • Static and architectural reviews of protocol handlers for missing authentication checks on command dispatch paths
  • Code review signals such as authorization being applied only to session setup or selected commands
  • Network monitoring for unauthenticated connections and data operations on the MongoDB listener
  • Policy enforcement requiring database endpoints to be private, authenticated, and covered by access-control tests
  • Automated security testing or code-scanning tools that model missing authentication and authorization paths

Sources

SourceLink
github.comgithub.com/ArcadeData/arcadedb/security/advisories/GHSA-fq9c-x968-g278
vulncheck.comvulncheck.com/advisories/arcadedb-mongodb-wire-protocol-authentication-bypass-cross-database

Frequently asked

questions

Yes, when the MongoDB wire-protocol listener is reachable over the network. The attacker does not need credentials if the vulnerable command path accepts unauthenticated requests.

The primary requirement is network connectivity to the ArcadeDB listener, commonly port 27017. Local access, an application account, or database credentials may not be necessary.

Require successful authentication and command-level authorization before processing every data and administrative operation, while also restricting network exposure.

Use deny-by-default protocol handlers, test unauthenticated behavior for every sensitive command, apply least privilege, and continuously monitor database endpoints for unexpected anonymous activity.

Find out what's already
exploitable in your codebase.