<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 22 Nov 2026 23:14:23 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-409067</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-409067</link>
      <description>EUVD-2026-409067</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-409067</guid>
    </item>
    <item>
      <title>fkie_cve-2026-77283</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-77283</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-77283</guid>
    </item>
    <item>
      <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>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mx6p-3fg7-v6pj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: obsidian-sync-mcp&lt;/p&gt;
&lt;p&gt;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&amp;#39;s &amp;#34;local network only&amp;#34; 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&amp;#39;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).&lt;/p&gt;
&lt;p&gt;Affected versions: &amp;lt;= 0.5.6
Patched version: 0.5.7&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Any deployment running without MCP_AUTH_TOKEN — including the README &amp;#34;Filesystem mode (simplest)&amp;#34; quickstart and the self-hosted docker-compose setup (where MCP_AUTH_TOKEN defaults to empty)&amp;#34; — is exposed to any website the operator visits while the server is running. That page&amp;#39;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.&lt;/p&gt;
&lt;p&gt;## Remediation&lt;/p&gt;
&lt;p&gt;Upgrade to 0.5.7, which validates both the Host and Origin headers in no-auth mode: any request whose…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: obsidian-sync-mcp&lt;/p&gt;
&lt;p&gt;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&amp;#39;s &amp;#34;local network only&amp;#34; 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&amp;#39;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).&lt;/p&gt;
&lt;p&gt;Affected versions: &amp;lt;= 0.5.6
Patched version: 0.5.7&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Any deployment running without MCP_AUTH_TOKEN — including the README &amp;#34;Filesystem mode (simplest)&amp;#34; quickstart and the self-hosted docker-compose setup (where MCP_AUTH_TOKEN defaults to empty)&amp;#34; — is exposed to any website the operator visits while the server is running. That page&amp;#39;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.&lt;/p&gt;
&lt;p&gt;## Remediation&lt;/p&gt;
&lt;p&gt;Upgrade to 0.5.7, which validates both the Host and Origin headers in no-auth mode: any request whose…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mx6p-3fg7-v6pj</guid>
    </item>
  </channel>
</rss>
