Vulnerabilities in pkg:npm/@bitbonsai/mcpvault
PACKAGECVE-2026-57442 is a MODERATE pathfilter restricted directories (.git/.obsidian/node_modules) only vulnerability (CWE-538: Insertion of Sensitive Information into Externally-Accessible File or Directory) affecting MCPVault libraries in the npm ecosystem. The issue involves pathfilter restricted directories (.git/.obsidian/node_modules) only denied at vault root, not nested. Remediation is available by upgrading affected packages to version 0.11.5.
pkg:npm/@bitbonsai/mcpvault
Vulnerability advisories affecting package pkg:npm/@bitbonsai/mcpvault. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-9c83-rr99-vfwj | CVE-2026-57442 | MODERATE | MCPVault: PathFilter restricted directories (.git/.obsidian/node_modules) only denied at vault root, not nested |
| GHSA-j99q-93c9-h869 | CVE-2026-57441 | MODERATE | MCPVault: PathFilter restricted-directory deny-list bypass via case and trailing dot/space equivalence |
CVE-2026-57442 at a Glance
How to Fix CVE-2026-57442
To remediate this vulnerability, upgrade all affected MCPVault dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @bitbonsai/mcpvault@0.11.5
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @bitbonsai/mcpvault
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-57442, inspect your project dependencies using npm:
npm ls @bitbonsai/mcpvault
Analyze the terminal output to locate any version of MCPVault in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.11.5), your application is affected.
Note: The npm ls @bitbonsai/mcpvault command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-538: Insertion of Sensitive Information into Externally-Accessible File or Directory, where the product places sensitive information into files or directories that are accessible to actors who are allowed to have access to the files, but not to the sensitive information. In MCPVault, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-57442 Affected MCPVault Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@bitbonsai/mcpvault
|
npm |
< 0.11.5
|
0.11.5
|
References
Frequently Asked Questions
What is CVE-2026-57442?
Which MCPVault versions are affected?
What version fixes CVE-2026-57442?
Is @bitbonsai/mcpvault affected?
What CWE is associated with CVE-2026-57442?
How can I check npm dependencies for CVE-2026-57442?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-9c83-rr99-vfwj",
"modified" : "2026-07-20T21:31:20Z",
"published" : "2026-06-19T21:42:24Z",
"aliases" : [ "CVE-2026-57442" ],
"summary" : "MCPVault: PathFilter restricted directories (.git/.obsidian/node_modules) only denied at vault root, not nested",
"details" : "PathFilter's deny-list glob patterns are anchored, so `.git`, `.obsidian`, and `node_modules` were only blocked at the vault root. Nested copies inside the vault (e.g. `tools/cli/node_modules/...`, `tools/somerepo/.git/config`, a nested `.obsidian/`) were fully traversable via isAllowed/isAllowedForListing. Impact: a nested `.git/config` (remote URLs / embedded tokens) and nested `.obsidian` contents could be read, under the same prompt-injection threat model as GHSA-j99q-93c9-h869 (an attacker influences the path an agent reads). It also caused nested `node_modules` to pollute the tag index (#128, the public symptom). Fixed in 0.11.5 by denying these restricted names at any path depth (matched case-insensitively as any path segment).",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@bitbonsai/mcpvault"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.11.5"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/bitbonsai/mcpvault/security/advisories/GHSA-9c83-rr99-vfwj"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/bitbonsai/mcpvault"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-22", "CWE-538" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-06-19T21:42:24Z",
"nvd_published_at" : null
}
}