CVE-2026-57442: MCPVault: PathFilter restricted directories (.git/.obsidian/node_modules) only denied at vault root, not nested
PathFilter's deny-list glob patterns are anchored, so .git, .obsidian, and nodemodules were only blocked at the vault root. Nested copies inside the vault (e.g. tools/cli/nodemodules/..., tools/somerepo/.git/config, a nested .obsidian/) were fully traversable via isAllowed/isAllowedForListing.
Published Jun 19, 2026 · Updated Jul 20, 2026
Affected packages
@bitbonsai/mcpvault
- Ecosystem
- npm
- Affected
- < 0.11.5
- Fixed in
- 0.11.5
- Check
npm ls @bitbonsai/mcpvault
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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).
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
