How severe is GHSA-j99q-93c9-h869?

No CVSS score has been assigned to GHSA-j99q-93c9-h869 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j99q-93c9-h869?

GHSA-j99q-93c9-h869 affects the following packages: @bitbonsai/mcpvault (npm). Ecosystems affected: npm.

How do I fix GHSA-j99q-93c9-h869?

Update @bitbonsai/mcpvault to 0.11.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j99q-93c9-h869 is resolved across your whole dependency graph.

How do I detect GHSA-j99q-93c9-h869 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @bitbonsai/mcpvault, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-j99q-93c9-h869 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-j99q-93c9-h869 actively exploited in the wild?

No public exploit code has been indexed for GHSA-j99q-93c9-h869 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-j99q-93c9-h869?

GHSA-j99q-93c9-h869 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 10th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-j99q-93c9-h869?

GHSA-j99q-93c9-h869 is classified as CWE-41 (CWE-41), CWE-178 (CWE-178). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-j99q-93c9-h869 published, and has it been updated?

GHSA-j99q-93c9-h869 was published on June 18, 2026 and was last updated on July 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

MCPVault: PathFilter restricted-directory deny-list bypass via case and trailing dot/space equivalenceGHSA-j99q-93c9-h869

GHSA-j99q-93c9-h869 is a CWE-41 vulnerability in @bitbonsai/mcpvault. A fix is available for @bitbonsai/mcpvault — see the affected versions and patch details below.

Also known asCVE-2026-57441

Published

Jun 18, 2026

Updated

Jul 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-j99q-93c9-h869.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs10th percentile — riskier than 10% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@bitbonsai/mcpvaultnpm

13Kdownloads / week

Description

MCPVault is a lightweight Model Context Protocol server for safe access to files in an Obsidian vault. Prior to 0.11.4, PathFilter in src/pathfilter.ts compiles restricted-directory patterns case-sensitively and compares paths without canonicalizing filesystem-equivalent segment names. On case-insensitive macOS and Windows filesystems, case variants of .git, .obsidian, or node_modules pass both isAllowed() and isAllowedForListing() even though the operating system opens the restricted directory, and Windows trailing dots or spaces provide the same bypass. An attacker who influences a path selected by an AI agent can use the bypass in read, write, move, search, or listing operations to expose or modify sensitive repository and Obsidian metadata. Vault-root .. containment is not affected. This issue is fixed in version 0.11.4.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@bitbonsai/mcpvault`	all versions	0.11.4`npm install @bitbonsai/mcpvault@0.11.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @bitbonsai/mcpvault, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @bitbonsai/mcpvault to 0.11.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j99q-93c9-h869 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

On case-insensitive filesystems (macOS, Windows), PathFilter compiled its deny-list patterns case-sensitively and matched the path verbatim, so names like `.Git/config`, `.GIT/config`, or `.oBsIdIaN/secrets.md` slipped past the `.git`/`.obsidian`/`node_modules` restriction while the OS opened the real file. On Windows, trailing dots/spaces (`.git./config`, `.git /config`) bypassed it the same way. Affects both `isAllowed` (read/write/move/search) and `isAllowedForListing`. Vault-root `..` containment is NOT affected. Fixed in 0.11.4 by case-insensitive matching plus per-segment canonicalizatio

O3 Security · Impact-Aware SCA

Is GHSA-j99q-93c9-h869 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works