# CVE-2026-8063: Post-auth null pointer dereference when aggregating against a view with empty search pipeline

> An authenticated user can crash the MongoDB server by running specific aggregation stages with an empty pipeline on a view.

- **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:** 7 May 2026
- **Updated:** 7 May 2026
- **Also known as:** BIT-mongodb-2026-8063, GHSA-v547-m6pg-pf7w

## What is CVE-2026-8063?

CVE-2026-8063 is a high-severity vulnerability in Mongodb Mongodb, published on 7 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An authenticated user can crash mongod when running $rankFusion or $scoreFusion with an empty pipeline on a view.

When resolving a view, the server inspects the aggregation pipeline to determine whether it begins with an Atlas Search stage. For $rankFusion and $scoreFusion, this inspection reads the first element on each stage’s input pipeline array without first verifying that the array is non-empty. Supplying an empty pipeline causes a null pointer dereference and crashes the server.

This issue affects MongoDB Server 8.2 versions prior to 8.2.7.

Weakness: CWE-476 (NULL Pointer Dereference)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mongodb` | Bitnami | From 8.2.0 | 8.2.7 |

Products: Mongodb Mongodb.

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

Upgrade mongodb to 8.2.7 or later.

## Is CVE-2026-8063 being exploited?

There is no known exploitation of CVE-2026-8063 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-8063 and fix it if it is affected.

What it is: CVE-2026-8063 is a high-severity vulnerability in Mongodb Mongodb, published on 7 May 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-8063 in the wild and no public exploit code.

Affected packages and fixed versions:
- mongodb (Bitnami): affected from 8.2.0; fixed in 8.2.7

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

## Sources

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

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