# CVE-2026-82058: Unhandled Exception in MongoDB Server JSON Schema Validation Error Generation Leads to Denial of Service

> An authenticated user can crash the MongoDB server by submitting a malformed BSON document that triggers an unhandled exception during JSON Schema validation.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **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-82058, GHSA-r492-gcgw-xqm5, MINI-637w-3hm6-v5h9, MINI-fhx9-wq6m-xrj5, MINI-vrcv-8qqp-vf4c, UBUNTU-CVE-2026-82058

## What is CVE-2026-82058?

CVE-2026-82058 is a high-severity denial of service vulnerability in Mongodb Mongodb, published on 8 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw in MongoDB's JSON Schema validation error generation code allows an authenticated user with readWrite privileges to crash the mongod server. When a BSON document containing an array with a malformed numeric field name fails a $jsonSchema items type constraint, the error generation path performs unsafe numeric conversion on the user-controlled field name without proper exception handling, resulting in an uncaught exception that terminates the server process. This is possible because incoming wire protocol BSON validation does not enforce that array element field names are valid, in-range numeric indices.

Weakness: CWE-248 (Uncaught Exception)

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

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

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

## Is CVE-2026-82058 being exploited?

There is no known exploitation of CVE-2026-82058 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-82067](https://insights.sbomify.com/CVE-2026-82067/): Auth bypass in MongoDB Server (critical 9.2)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82058 is a high-severity denial of service vulnerability in Mongodb Mongodb, published on 8 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82058 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-82058/ (Markdown: https://insights.sbomify.com/CVE-2026-82058/index.md)
```

## Sources

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

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