# CVE-2026-132038: Rapid7 Metasploit Framework Local Privilege Escalation via Insecure msfdb PostgreSQL Configuration


- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-xfq9-5cm6-5p27

## What is CVE-2026-132038?

CVE-2026-132038 is a high-severity vulnerability in Rapid7 Metasploit Framework, published on 18 Nov 2026. 

### Official description

Rapid7 Metasploit Framework versions prior to 6.5.10 suffer from an Improper Access Control issue in the msfdb database initialisation component whereby a PostgreSQL cluster initialised via msfdb init is configured with trust authentication and a world-accessible Unix domain socket in /tmp, allowing any local user on the same host to authenticate as the passwordless postgres superuser and execute arbitrary operating system commands as the msfdb owner. 

This issue is fixed in version 6.5.10.

Weakness: CWE-284 (Improper Access Control)

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


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

Upgrade Rapid7 Metasploit Framework to 6.5.10 or later. The advisory says that version fixes it.

## Is CVE-2026-132038 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-132038 is a high-severity vulnerability in Rapid7 Metasploit Framework, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-132038 in the wild and no public exploit code.

Affected product: Rapid7 Metasploit Framework. 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-132038/ (Markdown: https://insights.sbomify.com/CVE-2026-132038/index.md)
```

## Sources

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

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