<?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>Tue, 17 Nov 2026 03:17:25 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-386165</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-386165</link>
      <description>EUVD-2026-386165</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-386165</guid>
    </item>
    <item>
      <title>fkie_cve-2026-77363</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-77363</link>
      <description>&lt;p&gt;obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. Prior to 1.3.1, the Streamable HTTP transport does not validate the Host or Origin header or enable DNS-rebinding protection. When the documented loopback configuration uses auth.mode set to none, a malicious web page can send requests to the local MCP endpoint and receive unrestricted vault access through the http-local caller. Version 1.3.1 fixes the vulnerability by enabling host, origin, and DNS-rebinding validation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;obsidian-tc is a governed, agent-ready Model Context Protocol server for Obsidian vaults. Prior to 1.3.1, the Streamable HTTP transport does not validate the Host or Origin header or enable DNS-rebinding protection. When the documented loopback configuration uses auth.mode set to none, a malicious web page can send requests to the local MCP endpoint and receive unrestricted vault access through the http-local caller. Version 1.3.1 fixes the vulnerability by enabling host, origin, and DNS-rebinding validation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-77363</guid>
    </item>
    <item>
      <title>GHSA-pqh8-4pj7-32xx — obsidian-tc HTTP transport lacks Origin/DNS-rebinding protection, enabling drive-by vault access on loopback</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pqh8-4pj7-32xx</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: obsidian-tc&lt;/p&gt;
&lt;p&gt;### Impact
The Streamable HTTP transport was constructed without `enableDnsRebindingProtection`/`allowedHosts`/`allowedOrigins` and performed no `Origin`-header validation. With the documented `auth.mode: &amp;#34;none&amp;#34;` loopback default, a **drive-by web page could `POST http://127.0.0.1/mcp`** and receive caller `http-local` with scopes `[&amp;#34;*&amp;#34;]` — full vault read/write — via DNS rebinding / a forged Origin.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in **1.3.1**. Upgrade to `&amp;gt;= 1.3.1`. The transport now enables DNS-rebinding protection and allowed hosts/origins and returns HTTP 403 on an invalid Origin (per MCP 2025-11-25).&lt;/p&gt;
&lt;p&gt;### Workarounds
Do not expose the HTTP transport with `auth.mode: &amp;#34;none&amp;#34;`; require JWT auth, or bind to a non-loopback interface behind a proxy that validates `Origin`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: obsidian-tc&lt;/p&gt;
&lt;p&gt;### Impact
The Streamable HTTP transport was constructed without `enableDnsRebindingProtection`/`allowedHosts`/`allowedOrigins` and performed no `Origin`-header validation. With the documented `auth.mode: &amp;#34;none&amp;#34;` loopback default, a **drive-by web page could `POST http://127.0.0.1/mcp`** and receive caller `http-local` with scopes `[&amp;#34;*&amp;#34;]` — full vault read/write — via DNS rebinding / a forged Origin.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in **1.3.1**. Upgrade to `&amp;gt;= 1.3.1`. The transport now enables DNS-rebinding protection and allowed hosts/origins and returns HTTP 403 on an invalid Origin (per MCP 2025-11-25).&lt;/p&gt;
&lt;p&gt;### Workarounds
Do not expose the HTTP transport with `auth.mode: &amp;#34;none&amp;#34;`; require JWT auth, or bind to a non-loopback interface behind a proxy that validates `Origin`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pqh8-4pj7-32xx</guid>
    </item>
  </channel>
</rss>
