<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-22T22:49:58.454121+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-409067</id>
    <title>EUVD-2026-409067</title>
    <updated>2026-11-22T22:49:58.456432+00:00</updated>
    <content>EUVD-2026-409067</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-409067"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-77283</id>
    <title>fkie_cve-2026-77283</title>
    <updated>2026-11-22T22:49:58.456462+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-77283"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-mx6p-3fg7-v6pj</id>
    <title>GHSA-mx6p-3fg7-v6pj — obsidian-sync-mcp: Missing Host/Origin validation lets a public website drive a victim's Obsidian vault via DNS rebindi…</title>
    <updated>2026-11-22T22:49:58.456495+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: obsidian-sync-mcp</p>
<p>When obsidian-sync-mcp runs without MCP_AUTH_TOKEN (the documented no-auth mode for local use), the HTTP MCP endpoint does not validate the Host or Origin header before dispatching MCP methods (CWE-350). The no-auth mode's "local network only" assumption therefore does not hold: a malicious web page the operator visits can use DNS rebinding to resolve an attacker-controlled hostname to 127.0.0.1 (or the operator's LAN/VPN/Docker-published address) and issue requests the server accepts as trusted local calls, reaching the full tool surface (read_note, write_note, edit_note, delete_note, move_note, list_notes, list_folders, list_tags, get_note_metadata).</p>
<p>Affected versions: &lt;= 0.5.6
Patched version: 0.5.7</p>
<p>## Impact</p>
<p>Any deployment running without MCP_AUTH_TOKEN — including the README "Filesystem mode (simplest)" quickstart and the self-hosted docker-compose setup (where MCP_AUTH_TOKEN defaults to empty)" — is exposed to any website the operator visits while the server is running. That page's JavaScript can silently read the entire vault and create/overwrite/delete/move notes, with no credentials and no prompt. In CouchDB/Self-hosted LiveSync mode, the same code path applies, so vault content in CouchDB is equally reachable. Deployments that set MCP_AUTH_TOKEN are not affected — a bearer token is not attached by browsers, so a forged request returns HTTP 401.</p>
<p>## Remediation</p>
<p>Upgrade to 0.5.7, which validates both the Host and Origin headers in no-auth mode: any request whose…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-mx6p-3fg7-v6pj"/>
  </entry>
</feed>
