Obsidian Web MCP is a secure remote MCP server for Obsidian vaults. Prior to 0.2.0, /oauth/authorize issues an authorization code without a login, consent, or session check, and /oauth/token can exchange that code for the static VAULT_MCP_TOKEN without authenticating a client. An unauthenticated remote caller who can reach the intended tunnel deployment can therefore call /mcp and use vault_read, vault_write, vault_search, vault_list, vault_move, and vault_delete against the entire vault. Optional PKCE does not prevent an attacker-initiated flow, and unauthenticated /oauth/register also exposes a client_credentials path by returning the configured VAULT_OAUTH_CLIENT_SECRET. This issue is fixed in version 0.2.0.
CVE-2026-54618
This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.4
- EG Score
- 9.4(medium)
- EG Risk
- 47(Track)EG Risk 47/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity94% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 34%
- KEV
- Not listed
Published
September 17, 2026
Last Modified
September 17, 2026
Advisory Details (4)
Auto-updated Sep 17, 2026v0.2.0 — security fix (#8, #29)
Patch available: jimprosser/obsidian-web-mcp v0.2.0
https://github.com/jimprosser/obsidian-web-mcp/releases/tag/v0.2.0commit e4924f096ee7 (jimprosser/obsidian-web-mcp)
Patch available: jimprosser/obsidian-web-mcp v0.2.0 (contains commit e4924f096ee7)
https://github.com/jimprosser/obsidian-web-mcp/commit/e4924f096ee7494a7999d6c0cceca9be08e48eefFix critical auth bypass: authenticate before issuing OAuth tokens (#8, #29)
Patch available: jimprosser/obsidian-web-mcp v0.2.0 (PR #30 merged 2026-06-07)
https://github.com/jimprosser/obsidian-web-mcp/pull/30Unauthenticated vault access: /oauth/authorize auto-approves without authenticating the user · Advisory · jimprosser/obsidian-web-mcp · GitHub
https://github.com/jimprosser/obsidian-web-mcp/security/advisories/GHSA-hwhg-mrjc-8g43Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 18:20 UTCEG score recompute
- 2026-09-18 23:06 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 20:18 UTCEG score recompute
- 2026-09-17 19:51 UTCEG score recompute
- 2026-09-17 19:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-522 · CWE-306
Frequently asked(5)
What is CVE-2026-54618?
When was CVE-2026-54618 disclosed?
Is CVE-2026-54618 actively exploited?
What is the CVSS score of CVE-2026-54618?
How do I remediate CVE-2026-54618?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-54618
Is Your Infrastructure Affected by CVE-2026-54618?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.