# CVE-2026-75852: ArcadeDB MongoDB wire protocol authentication bypass cross-database

> Unauthenticated attackers can read and modify data in any database via the MongoDB wire protocol due to missing SASL authentication enforcement.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-fq9c-x968-g278, GHSA-xgx7-2w7q-r9mc

## What is CVE-2026-75852?

CVE-2026-75852 is a critical authentication bypass vulnerability in ArcadeData arcadedb, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ArcadeDB versions before 26.8.1 fail to enforce SASL authentication on data commands in the MongoDB wire-protocol plugin. Unauthenticated attackers can issue insert, find, update, delete, and create commands against any database by connecting to port 27017 without credentials.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-75852?


## How do I fix CVE-2026-75852?

No fix has been published for CVE-2026-75852 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-75852 being exploited?

There is no known exploitation of CVE-2026-75852 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-75852 and fix it if it is affected.

What it is: CVE-2026-75852 is a critical authentication bypass vulnerability in ArcadeData arcadedb, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-75852 in the wild and no public exploit code.

Affected product: ArcadeData arcadedb. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-75852/ (Markdown: https://insights.sbomify.com/CVE-2026-75852/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-75852
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-75852
- OSV: https://osv.dev/vulnerability/CVE-2026-75852

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-75852/
Summaries are generated and may contain mistakes; the official description above is the record.