CVE-2026-77283

A web page could read or change an unauthenticated Obsidian MCP vault

es617 · obsidian-sync-mcp

First documented disclosure · Review checkpoint

Summary

A visited page could invoke vault tools through a locally reachable MCP endpoint.

Severity and exploitation evidence

High · 8.8/10 · CVSS 4.0. Severity source.

Exploitation not established: Malicious exploitation remains unverified in the reviewed originals. A demonstration or absence from KEV does not establish exploitation status.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

No-auth mode omitted authentication and Host/Origin validation.

Conditions required

obsidian-sync-mcp runs without MCP_AUTH_TOKEN and the operator visits malicious web content; browser reachability is required.

Potential impact

Vault notes can be read, created, overwritten, moved or deleted in filesystem or CouchDB mode.

Affected versions and configurations

obsidian-sync-mcp: < 0.5.7.

Fix and mitigation status

0.5.7; setting MCP_AUTH_TOKEN also closes the described browser path.

Practical next steps

Apply the issue-specific correction: 0.5.7; setting MCP_AUTH_TOKEN also closes the described browser path. Restrict the affected tool or endpoint until the correction is deployed.

Operating lesson

Require authentication on untrusted networks and validate browser boundaries for local services.

Evidence and limits

Earliest reviewed public evidence 2026-07-10; CVE publication 2026-11-18. CVSS 4.0 8.8 is attributed to GitHub_M in the CNA record.

Sources