Skip to main content
VulnerabilityPublished

CVE-2026-77283: es617 obsidian-sync-mcp · Reliance on Reverse DNS Resolution for a Security-Critical Action

Affects es617 obsidian-sync-mcpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 0.5.7 soon.

Data as of 18 Nov 2026, 23:19 UTC

CVSS 4.0 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.08.8
Patch
Available – fixed in 0.5.7
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade obsidian-sync-mcp and es617/obsidian-sync-mcp to 0.5.7.

Affected software

ProductAffectedFixed in
es617obsidian-sync-mcpAffected
  • <0.5.7
Fixed in
  • 0.5.7
GitHubes617/obsidian-sync-mcppkg:github/es617/obsidian-sync-mcpOther threatsAffected
  • <0.5.7
Fixed in
  • 0.5.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade obsidian-sync-mcp to version 0.5.7 or later, where the authentication check for the /mcp endpoint is enforced. Deployments using MCP_AUTH_TOKEN are not affected by this vulnerability. No additional mitigation is required for those deployments.

Description

A vulnerability in obsidian-sync-mcp versions prior to 0.5.7 allows unauthenticated HTTP requests to the /mcp endpoint without validating Host or Origin headers. This enables DNS rebinding or cross-origin attacks from malicious websites to access and manipulate Obsidian vault notes. Deployments using MCP_AUTH_TOKEN are not affected. The issue is fixed in version 0.5.7.

References

Community reviews

Loading reviews…