# CVE-2026-13067: tlsCATrusts Role Restriction Not Enforced via PROXY Protocol v2 on Unix Domain Socket

> Attackers with local socket access and valid certificates can bypass role restrictions, gaining unintended privileges in MongoDB.

- **Severity:** High 7.2 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** BIT-mongodb-2026-13067, GHSA-fcc5-5hp3-gxp7, MINI-8gch-vw7j-3cm9, MINI-vx38-hcj8-7g53, UBUNTU-CVE-2026-13067

## What is CVE-2026-13067?

CVE-2026-13067 is a high-severity authentication bypass vulnerability in Mongodb Mongodb, published on 22 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

When PROXY protocol v2 is used on the Unix domain socket path, roles derived from X.509 client certificates may not be validated against the configured tlsCATrusts allow-list. This can result in unintended role assignments following MONGODB-X509 authentication. Affected scenarios require local access to the proxy Unix domain socket and a valid X.509 certificate issued by a trusted certificate authority.

Weakness: CWE-863 (Incorrect Authorization)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mongodb` | Bitnami | From 8.0.0 | 8.0.28, 8.3.7 |

Products: Mongodb Mongodb.

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

Upgrade mongodb to a fixed version for your release line: 8.0.28 or 8.3.7.

## Is CVE-2026-13067 being exploited?

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

What it is: CVE-2026-13067 is a high-severity authentication bypass vulnerability in Mongodb Mongodb, published on 22 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-13067 in the wild and no public exploit code.

Affected packages and fixed versions:
- mongodb (Bitnami): affected from 8.0.0; fixed in 8.0.28, 8.3.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-13067/ (Markdown: https://insights.sbomify.com/CVE-2026-13067/index.md)
```

## Sources

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

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