<?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://vulnerability.circl.lu</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>Sun, 04 Oct 2026 14:35:23 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-100537</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-100537</link>
      <description>&lt;p&gt;OpenClaw (npm package &amp;#39;openclaw&amp;#39;) before 2026.8.1 fails to apply the originating requester&amp;#39;s effective tool policy during Active Memory automatic recall. In deployments that use Active Memory together with requester-specific tool rules, deterministic and hidden recall paths can retrieve durable memory and inject it into the agent&amp;#39;s context even when toolsBySender explicitly denies that requester access to the memory tools (memory_search, memory_get). As a result, an admitted but denied sender can receive information derived from durable memory in the agent&amp;#39;s response without directly invoking any memory tool. The issue is fixed in 2026.8.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenClaw (npm package &amp;#39;openclaw&amp;#39;) before 2026.8.1 fails to apply the originating requester&amp;#39;s effective tool policy during Active Memory automatic recall. In deployments that use Active Memory together with requester-specific tool rules, deterministic and hidden recall paths can retrieve durable memory and inject it into the agent&amp;#39;s context even when toolsBySender explicitly denies that requester access to the memory tools (memory_search, memory_get). As a result, an admitted but denied sender can receive information derived from durable memory in the agent&amp;#39;s response without directly invoking any memory tool. The issue is fixed in 2026.8.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-100537</guid>
    </item>
    <item>
      <title>GHSA-368p-92qh-j8q4</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-368p-92qh-j8q4</link>
      <description>&lt;p&gt;OpenClaw (npm package &amp;#39;openclaw&amp;#39;) before 2026.8.1 fails to apply the originating requester&amp;#39;s effective tool policy during Active Memory automatic recall. In deployments that use Active Memory together with requester-specific tool rules, deterministic and hidden recall paths can retrieve durable memory and inject it into the agent&amp;#39;s context even when toolsBySender explicitly denies that requester access to the memory tools (memory_search, memory_get). As a result, an admitted but denied sender can receive information derived from durable memory in the agent&amp;#39;s response without directly invoking any memory tool. The issue is fixed in 2026.8.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenClaw (npm package &amp;#39;openclaw&amp;#39;) before 2026.8.1 fails to apply the originating requester&amp;#39;s effective tool policy during Active Memory automatic recall. In deployments that use Active Memory together with requester-specific tool rules, deterministic and hidden recall paths can retrieve durable memory and inject it into the agent&amp;#39;s context even when toolsBySender explicitly denies that requester access to the memory tools (memory_search, memory_get). As a result, an admitted but denied sender can receive information derived from durable memory in the agent&amp;#39;s response without directly invoking any memory tool. The issue is fixed in 2026.8.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-368p-92qh-j8q4</guid>
    </item>
  </channel>
</rss>
