# CVE-2026-82067: Auth bypass in MongoDB Server

> An unauthenticated attacker can bypass authorization checks due to case sensitivity flaws, gaining full administrative control over the database.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/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:** Yes
- **Published:** 8 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** BIT-mongodb-2026-82067, GHSA-rg3j-hvqv-ccpr, MINI-2gw8-7v5j-c4h4, MINI-8h6m-h56p-cx6c, MINI-9fv5-r35v-7w8p, UBUNTU-CVE-2026-82067

## What is CVE-2026-82067?

CVE-2026-82067 is a critical authentication bypass vulnerability in Mongodb Mongodb, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper handling of case sensitivity in the configuration validation component of MongoDB Server may cause the authorization subsystem to remain in a default disabled state during server startup. An unauthenticated user with network access to a deployment where this condition occurs can perform arbitrary administrative operations, resulting in full impact of data confidentiality, integrity, and availability.

Weakness: CWE-178 (Improper Handling of Case Sensitivity)

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

1 open source package ship an affected version, including mongodb. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mongodb` | Bitnami | From 7.0.0 | 7.0.41, 8.0.30, 8.3.9 |

Products: Mongodb Mongodb.

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

Upgrade mongodb to a fixed version for your release line: 7.0.41, 8.0.30 or 8.3.9.

## Is CVE-2026-82067 being exploited?

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

## Other vulnerabilities in Mongodb Mongodb

- [CVE-2025-14847](https://insights.sbomify.com/CVE-2025-14847/): MongoDB and MongoDB Server Improper Handling of Length Parameter Inconsistency (high 8.7, exploited in the wild)
- [CVE-2026-13072](https://insights.sbomify.com/CVE-2026-13072/): MongoDB Improper Input Validation in Compute Mode External Data Processing Leading to Memory Corruption (critical 9.2)
- [CVE-2017-15535](https://insights.sbomify.com/CVE-2017-15535/): Denial of service in n/a (critical 9.1)
- [CVE-2026-18691](https://insights.sbomify.com/CVE-2026-18691/): Improper Authentication in MongoDB Intra-Cluster Connections Allows Credential Exposure (critical 9.0)
- [CVE-2024-1351](https://insights.sbomify.com/CVE-2024-1351/): MongoDB Server may allow successful untrusted connection (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82067 is a critical authentication bypass vulnerability in Mongodb Mongodb, published on 8 Sep 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-82067 in the wild and no public exploit code.

Affected packages and fixed versions:
- mongodb (Bitnami): affected from 7.0.0; fixed in 7.0.41, 8.0.30, 8.3.9

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-82067/ (Markdown: https://insights.sbomify.com/CVE-2026-82067/index.md)
```

## Sources

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

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