# CVE-2026-57442: MCPVault: PathFilter restricted directories (.git/.obsidian/node_modules) only denied at vault root, not nested

> An attacker can bypass path restrictions to read sensitive nested files like .git or .obsidian metadata in MCPVault.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-9c83-rr99-vfwj

## What is CVE-2026-57442?

CVE-2026-57442 is a medium-severity path traversal vulnerability in bitbonsai mcpvault, published on 15 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

MCPVault is a lightweight Model Context Protocol server for safe access to files in an Obsidian vault. Prior to 0.11.5, PathFilter in src/pathfilter.ts uses root-anchored deny-list patterns, so nested .git, .obsidian, and node_modules path segments do not match the restriction and pass both isAllowed() and isAllowedForListing(). An attacker who influences a path selected by an AI agent can traverse nested repository or Obsidian metadata, read remote URLs or embedded tokens, or cause nested node_modules content to pollute the listAllTags index. This issue is fixed in version 0.11.5.

Weakness: CWE-538 (Insertion of Sensitive Information into Externally-Accessible File or Directory), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

2 open source packages ship an affected version, including @bitbonsai/mcpvault.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@bitbonsai/mcpvault` | npm | All versions | 0.11.5 |
| `@bitbonsai/mcpvault` | npm | All versions | 0.11.5 |

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

Upgrade @bitbonsai/mcpvault to 0.11.5 or later.

## Is CVE-2026-57442 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-57442 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-57442 is a medium-severity path traversal vulnerability in bitbonsai mcpvault, published on 15 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-57442 exists.

Affected packages and fixed versions:
- @bitbonsai/mcpvault (npm): affected all versions; fixed in 0.11.5
- @bitbonsai/mcpvault (npm): affected all versions; fixed in 0.11.5

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

## Sources

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

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