<?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 05:53:47 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-398449</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-398449</link>
      <description>EUVD-2026-398449</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-398449</guid>
    </item>
    <item>
      <title>fkie_cve-2026-115419</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-115419</link>
      <description>&lt;p&gt;The A2A server component in Amazon Strands Agents SDK for Python before 1.43.0 and Amazon Strands Agents SDK for TypeScript before 1.5.0 does not properly isolate conversation state between callers. An authenticated remote user could read other tenants&amp;#39; conversation history and add persistent instructions that alter model behavior for subsequent callers via HTTP requests to the A2A endpoint using a different context_id.&lt;/p&gt;
&lt;p&gt;To mitigate this issue, users should upgrade to strands-agents 1.43.0 (Python) or @strands-agents/sdk 1.5.0 (TypeScript).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The A2A server component in Amazon Strands Agents SDK for Python before 1.43.0 and Amazon Strands Agents SDK for TypeScript before 1.5.0 does not properly isolate conversation state between callers. An authenticated remote user could read other tenants&amp;#39; conversation history and add persistent instructions that alter model behavior for subsequent callers via HTTP requests to the A2A endpoint using a different context_id.&lt;/p&gt;
&lt;p&gt;To mitigate this issue, users should upgrade to strands-agents 1.43.0 (Python) or @strands-agents/sdk 1.5.0 (TypeScript).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-115419</guid>
    </item>
    <item>
      <title>GHSA-4v6f-7vjh-6x4m — Strands Agents SDK: Exposure of data element to wrong session in the A2A Server</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4v6f-7vjh-6x4m</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: strands-agents, npm: @strands-agents/sdk&lt;/p&gt;
&lt;p&gt;**Summary**  
Strands Agents SDK is an open-source SDK, available for Python (strands-agents) and TypeScript (@strands-agents/sdk), for building and running AI agents. An issue exists where, under certain circumstances, the Agent2Agent (A2A) server shares conversation history across callers with different context\_id values, allowing one caller to read and influence another caller&amp;#39;s session.  
  
**Impact**  
The A2A server did not properly isolate conversation state between callers. In multi-tenant deployments, an authenticated remote user could access another caller&amp;#39;s conversation history or influence model behavior for other callers (CWE-488: Unintended Disclosure of Data Element to Wrong Session). This affects any deployment where an A2A server is reachable by more than one user or tenant.  
  
**Impacted versions:**  
strands-agents (Python): all versions containing the multiagent.a2a module, &amp;lt; 1.43.0  
@strands-agents/sdk (TypeScript): &amp;lt; 1.5.0  
  
**Patches**  
This issue has been addressed in strands-agents version 1.43.0 and @strands-agents/sdk version 1.5.0. The A2A server now uses an agent factory so conversation state is isolated per A2A context\_id. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.  
  
**Workarounds**  
There is no workaround that fully addresses this issue in affected versions. Until you upgrade, do not expose an A2A server to more than one user or tenant. If multip…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: strands-agents, npm: @strands-agents/sdk&lt;/p&gt;
&lt;p&gt;**Summary**  
Strands Agents SDK is an open-source SDK, available for Python (strands-agents) and TypeScript (@strands-agents/sdk), for building and running AI agents. An issue exists where, under certain circumstances, the Agent2Agent (A2A) server shares conversation history across callers with different context\_id values, allowing one caller to read and influence another caller&amp;#39;s session.  
  
**Impact**  
The A2A server did not properly isolate conversation state between callers. In multi-tenant deployments, an authenticated remote user could access another caller&amp;#39;s conversation history or influence model behavior for other callers (CWE-488: Unintended Disclosure of Data Element to Wrong Session). This affects any deployment where an A2A server is reachable by more than one user or tenant.  
  
**Impacted versions:**  
strands-agents (Python): all versions containing the multiagent.a2a module, &amp;lt; 1.43.0  
@strands-agents/sdk (TypeScript): &amp;lt; 1.5.0  
  
**Patches**  
This issue has been addressed in strands-agents version 1.43.0 and @strands-agents/sdk version 1.5.0. The A2A server now uses an agent factory so conversation state is isolated per A2A context\_id. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.  
  
**Workarounds**  
There is no workaround that fully addresses this issue in affected versions. Until you upgrade, do not expose an A2A server to more than one user or tenant. If multip…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4v6f-7vjh-6x4m</guid>
    </item>
  </channel>
</rss>
