# CVE-2026-77283 — es617 obsidian-sync-mcp

> As of 2026-11-18, CVE-2026-77283 is a High-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in es617 obsidian-sync-mcp, CVSS v4.0 8.8. No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-77283 as of 2026-11-18; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-11-18

## What is CVE-2026-77283?

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.

The record classifies CVE-2026-77283 under weakness class [CWE-350](https://cwe.mitre.org/data/definitions/350.html). 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 1 day ago.

## Severity and exploitation probability

- **CVSS v4.0 base score:** 8.8 — High (derived from score) (`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`)
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 4.4/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-11-18

## Is CVE-2026-77283 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **es617**: obsidian-sync-mcp

## How to fix CVE-2026-77283

No vendor patch reference has been recorded for CVE-2026-77283 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-77283

No threat campaign in the Threadlinqs corpus currently references CVE-2026-77283, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com](https://github.com/es617/obsidian-sync-mcp/security/advisories/GHSA-mx6p-3fg7-v6pj)

**Other references**

- [github.com](https://github.com/es617/obsidian-sync-mcp/commit/d4d2cbbb02ffadaecf1d6252902b8d08610c7018)
- [github.com (v0.5)](https://github.com/es617/obsidian-sync-mcp/releases/tag/v0.5.7)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-77283
No Threadlinqs detection currently covers CVE-2026-77283; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
