<?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, 06 Oct 2026 18:31:40 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-327350</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-327350</link>
      <description>EUVD-2026-327350</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-327350</guid>
    </item>
    <item>
      <title>fkie_cve-2026-50287</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-50287</link>
      <description>&lt;p&gt;AgenticMail gives AI agents real email addresses and phone numbers. Prior to version 0.9.27, @agenticmail/mcp exposes a Streamable HTTP transport when started with --http or MCP_HTTP=1. In that mode, the /mcp endpoint accepts requests without any HTTP authentication layer. A remote client can initialize a session and call tools directly. This issue has been patched in version 0.9.27.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;AgenticMail gives AI agents real email addresses and phone numbers. Prior to version 0.9.27, @agenticmail/mcp exposes a Streamable HTTP transport when started with --http or MCP_HTTP=1. In that mode, the /mcp endpoint accepts requests without any HTTP authentication layer. A remote client can initialize a session and call tools directly. This issue has been patched in version 0.9.27.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-50287</guid>
    </item>
    <item>
      <title>GHSA-63gr-g7jc-v8rg — @agenticmail/mcp Missing Authentication for Critical Function</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-63gr-g7jc-v8rg</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @agenticmail/mcp&lt;/p&gt;
&lt;p&gt;# AgenticMail MCP HTTP authorization bypass&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`@agenticmail/mcp` exposes a Streamable HTTP transport when started with
`--http` or `MCP_HTTP=1`. In that mode, the `/mcp` endpoint accepts requests
without any HTTP authentication layer. A remote client can initialize a
session and call tools directly.&lt;/p&gt;
&lt;p&gt;The problem is that the MCP server also exposes tools documented as requiring
`AGENTICMAIL_MASTER_KEY`, and the server process forwards those calls using its
own configured master key. As a result, any client that can reach the MCP HTTP
port can invoke master-only operations without knowing the master key.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An unauthenticated network client can invoke master-key-only MCP tools through
the server, including administrative and gateway actions.&lt;/p&gt;
&lt;p&gt;Confirmed with a read-only tool:&lt;/p&gt;
&lt;p&gt;- `setup_guide`&lt;/p&gt;
&lt;p&gt;The same path reaches higher-impact tools such as:&lt;/p&gt;
&lt;p&gt;- `setup_email_relay`
- `setup_email_domain`
- `delete_agent`
- `cleanup_agents`
- `send_test_email`&lt;/p&gt;
&lt;p&gt;## Affected Code&lt;/p&gt;
&lt;p&gt;- `packages/mcp/src/index.ts`
- `packages/mcp/src/tools.ts`
- `packages/mcp/README.md`&lt;/p&gt;
&lt;p&gt;Relevant observations:&lt;/p&gt;
&lt;p&gt;- `packages/mcp/src/index.ts` starts an HTTP server for `/mcp` without
  checking an Authorization header.
- `packages/mcp/src/tools.ts` marks gateway/admin tools as master-key tools
  and forwards them with the server-side `AGENTICMAIL_MASTER_KEY`.
- `packages/mcp/README.md` documents that gateway/admin tools require the
  master key.&lt;/p&gt;
&lt;p&gt;## Reproduction&lt;/p&gt;
&lt;p&gt;Use the bundled one-command PoC runne…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @agenticmail/mcp&lt;/p&gt;
&lt;p&gt;# AgenticMail MCP HTTP authorization bypass&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`@agenticmail/mcp` exposes a Streamable HTTP transport when started with
`--http` or `MCP_HTTP=1`. In that mode, the `/mcp` endpoint accepts requests
without any HTTP authentication layer. A remote client can initialize a
session and call tools directly.&lt;/p&gt;
&lt;p&gt;The problem is that the MCP server also exposes tools documented as requiring
`AGENTICMAIL_MASTER_KEY`, and the server process forwards those calls using its
own configured master key. As a result, any client that can reach the MCP HTTP
port can invoke master-only operations without knowing the master key.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An unauthenticated network client can invoke master-key-only MCP tools through
the server, including administrative and gateway actions.&lt;/p&gt;
&lt;p&gt;Confirmed with a read-only tool:&lt;/p&gt;
&lt;p&gt;- `setup_guide`&lt;/p&gt;
&lt;p&gt;The same path reaches higher-impact tools such as:&lt;/p&gt;
&lt;p&gt;- `setup_email_relay`
- `setup_email_domain`
- `delete_agent`
- `cleanup_agents`
- `send_test_email`&lt;/p&gt;
&lt;p&gt;## Affected Code&lt;/p&gt;
&lt;p&gt;- `packages/mcp/src/index.ts`
- `packages/mcp/src/tools.ts`
- `packages/mcp/README.md`&lt;/p&gt;
&lt;p&gt;Relevant observations:&lt;/p&gt;
&lt;p&gt;- `packages/mcp/src/index.ts` starts an HTTP server for `/mcp` without
  checking an Authorization header.
- `packages/mcp/src/tools.ts` marks gateway/admin tools as master-key tools
  and forwards them with the server-side `AGENTICMAIL_MASTER_KEY`.
- `packages/mcp/README.md` documents that gateway/admin tools require the
  master key.&lt;/p&gt;
&lt;p&gt;## Reproduction&lt;/p&gt;
&lt;p&gt;Use the bundled one-command PoC runne…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-63gr-g7jc-v8rg</guid>
    </item>
  </channel>
</rss>
