<?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>Thu, 08 Oct 2026 23:32:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-1664 — Insecure Direct Object Reference (IDOR) via Header-Based Email Routing</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-1664</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; agents&lt;/p&gt;
&lt;p&gt;Summary&lt;/p&gt;
&lt;p&gt;An Insecure Direct Object Reference has been found to exist in `createHeaderBasedEmailResolver()` function within the Cloudflare Agents SDK. The issue occurs because the `Message-ID` and `References` headers are parsed to derive the target agentName and agentId without proper validation or origin checks, allowing an external attacker with control of these headers to route inbound mail to arbitrary Durable Object instances and namespaces .&lt;/p&gt;
&lt;p&gt;Root cause&lt;/p&gt;
&lt;p&gt;The `createHeaderBasedEmailResolver()` function lacks cryptographic verification or origin validation for the headers used in the routing logic, effectively allowing external input to dictate internal object routing.&lt;/p&gt;
&lt;p&gt;Impact&lt;/p&gt;
&lt;p&gt;Insecure Direct Object Reference (IDOR) in email routing lets an attacker steer inbound mail to arbitrary Agent instances via spoofed Message-ID.&lt;/p&gt;
&lt;p&gt;Mitigation:&lt;/p&gt;
&lt;p&gt;*  PR:  https://github.com/cloudflare/agents/blob/main/docs/email.md ] provides the necessary architectural context for coding agents to mitigate the issue by refactoring the resolver to enforce strict identity boundaries.
  *  Agents-sdk users should  upgrade to agents@0.3.7&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; agents&lt;/p&gt;
&lt;p&gt;Summary&lt;/p&gt;
&lt;p&gt;An Insecure Direct Object Reference has been found to exist in `createHeaderBasedEmailResolver()` function within the Cloudflare Agents SDK. The issue occurs because the `Message-ID` and `References` headers are parsed to derive the target agentName and agentId without proper validation or origin checks, allowing an external attacker with control of these headers to route inbound mail to arbitrary Durable Object instances and namespaces .&lt;/p&gt;
&lt;p&gt;Root cause&lt;/p&gt;
&lt;p&gt;The `createHeaderBasedEmailResolver()` function lacks cryptographic verification or origin validation for the headers used in the routing logic, effectively allowing external input to dictate internal object routing.&lt;/p&gt;
&lt;p&gt;Impact&lt;/p&gt;
&lt;p&gt;Insecure Direct Object Reference (IDOR) in email routing lets an attacker steer inbound mail to arbitrary Agent instances via spoofed Message-ID.&lt;/p&gt;
&lt;p&gt;Mitigation:&lt;/p&gt;
&lt;p&gt;*  PR:  https://github.com/cloudflare/agents/blob/main/docs/email.md ] provides the necessary architectural context for coding agents to mitigate the issue by refactoring the resolver to enforce strict identity boundaries.
  *  Agents-sdk users should  upgrade to agents@0.3.7&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-1664</guid>
    </item>
  </channel>
</rss>
