<?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-10-06T21:52:48.896558+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-327350</id>
    <title>EUVD-2026-327350</title>
    <updated>2026-10-06T21:52:48.944088+00:00</updated>
    <content>EUVD-2026-327350</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-327350"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-50287</id>
    <title>fkie_cve-2026-50287</title>
    <updated>2026-10-06T21:52:48.944127+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-50287"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-63gr-g7jc-v8rg</id>
    <title>GHSA-63gr-g7jc-v8rg — @agenticmail/mcp Missing Authentication for Critical Function</title>
    <updated>2026-10-06T21:52:48.944161+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @agenticmail/mcp</p>
<p># AgenticMail MCP HTTP authorization bypass</p>
<p>## Summary</p>
<p>`@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.</p>
<p>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.</p>
<p>## Impact</p>
<p>An unauthenticated network client can invoke master-key-only MCP tools through
the server, including administrative and gateway actions.</p>
<p>Confirmed with a read-only tool:</p>
<p>- `setup_guide`</p>
<p>The same path reaches higher-impact tools such as:</p>
<p>- `setup_email_relay`
- `setup_email_domain`
- `delete_agent`
- `cleanup_agents`
- `send_test_email`</p>
<p>## Affected Code</p>
<p>- `packages/mcp/src/index.ts`
- `packages/mcp/src/tools.ts`
- `packages/mcp/README.md`</p>
<p>Relevant observations:</p>
<p>- `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.</p>
<p>## Reproduction</p>
<p>Use the bundled one-command PoC runne…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-63gr-g7jc-v8rg"/>
  </entry>
</feed>
