CVE-2026-77283
Received Received - Intake

Remote Code Execution in Obsidian Sync MCP Server

Vulnerability report for CVE-2026-77283, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-18

Last updated on: 2026-11-18

Assigner: GitHub, Inc.

Description

obsidian-sync-mcp is an MCP server that gives AI agents access to Obsidian vaults. Prior to 0.5.7, deployments running without MCP_AUTH_TOKEN install no serverOptions.authenticate check for the HTTP /mcp endpoint, so requests are dispatched without validating the Host or Origin headers. A malicious website visited by the operator can use DNS rebinding to reach loopback, LAN, VPN, or container-published addresses, or directly issue a cross-origin request to loopback, and invoke the MCP tool surface to read, create, overwrite, delete, or move vault notes. Deployments using MCP_AUTH_TOKEN are not affected because browsers do not attach the bearer token. This issue is fixed in version 0.5.7.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-18
Last Modified
2026-11-18
Generated
2026-11-19
AI Q&A
2026-11-19
EPSS Evaluated
N/A
NVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
obsidian_sync_mcp obsidian_sync_mcp 0.5.7

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-350 The product performs reverse DNS resolution on an IP address to obtain the hostname and make a security decision, but it does not properly ensure that the IP address is truly associated with the hostname.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

obsidian-sync-mcp is an MCP server for accessing Obsidian vaults. Prior to version 0.5.7, deployments without MCP_AUTH_TOKEN lacked authentication checks for the HTTP /mcp endpoint. This allowed malicious websites to bypass host or origin validation via DNS rebinding or cross-origin requests, potentially accessing or modifying vault notes.

Detection Guidance

Check if your obsidian-sync-mcp version is below 0.5.7 by running: npm list obsidian-sync-mcp or checking package.json. Inspect network traffic for unexpected requests to /mcp endpoints from untrusted sources. Monitor for unauthorized file access or modifications in Obsidian vaults.

Impact Analysis

If you run obsidian-sync-mcp without MCP_AUTH_TOKEN, a malicious website could read, create, overwrite, delete, or move your Obsidian vault notes. This could lead to data loss, unauthorized access to sensitive information, or manipulation of your notes.

Compliance Impact

This vulnerability could lead to unauthorized access or modification of sensitive data, potentially violating GDPR (data protection) or HIPAA (health information privacy) requirements. Compliance may be impacted if user data is exposed or altered without authorization.

Mitigation Strategies

Upgrade to version 0.5.7 or later immediately. If using MCP_AUTH_TOKEN, ensure it is set and not exposed. Block external access to /mcp endpoints via firewall rules. Disable the MCP server if not needed. Review vault permissions and audit recent changes.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-77283. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...