<?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>Mon, 28 Sep 2026 10:27:39 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-100569</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-100569</link>
      <description>&lt;p&gt;OpenClaw is an npm-distributed application. In versions &amp;gt;= 2026.4.25 and &amp;lt; 2026.8.1, the workspace environment-variable filter did not block variables ending in `_ENDPOINT`, so an untrusted workspace `.env` file could set AZURE_SPEECH_ENDPOINT. Azure Speech preferred that value over the configured region, so when a synthesis or voice-list request was made, the attacker-selected endpoint received the operator&amp;#39;s Azure Speech key in the request header, allowing the key to be reused against the operator&amp;#39;s Azure Speech resource. Exploitation requires an operator to start OpenClaw in attacker-controlled workspace content with Azure Speech configured with a key and region and no trusted endpoint override set. The issue is fixed in 2026.8.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenClaw is an npm-distributed application. In versions &amp;gt;= 2026.4.25 and &amp;lt; 2026.8.1, the workspace environment-variable filter did not block variables ending in `_ENDPOINT`, so an untrusted workspace `.env` file could set AZURE_SPEECH_ENDPOINT. Azure Speech preferred that value over the configured region, so when a synthesis or voice-list request was made, the attacker-selected endpoint received the operator&amp;#39;s Azure Speech key in the request header, allowing the key to be reused against the operator&amp;#39;s Azure Speech resource. Exploitation requires an operator to start OpenClaw in attacker-controlled workspace content with Azure Speech configured with a key and region and no trusted endpoint override set. The issue is fixed in 2026.8.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-100569</guid>
    </item>
    <item>
      <title>GHSA-5cqq-r556-6vv9</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-5cqq-r556-6vv9</link>
      <description>&lt;p&gt;OpenClaw is an npm-distributed application. In versions &amp;gt;= 2026.4.25 and &amp;lt; 2026.8.1, the workspace environment-variable filter did not block variables ending in `_ENDPOINT`, so an untrusted workspace `.env` file could set AZURE_SPEECH_ENDPOINT. Azure Speech preferred that value over the configured region, so when a synthesis or voice-list request was made, the attacker-selected endpoint received the operator&amp;#39;s Azure Speech key in the request header, allowing the key to be reused against the operator&amp;#39;s Azure Speech resource. Exploitation requires an operator to start OpenClaw in attacker-controlled workspace content with Azure Speech configured with a key and region and no trusted endpoint override set. The issue is fixed in 2026.8.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenClaw is an npm-distributed application. In versions &amp;gt;= 2026.4.25 and &amp;lt; 2026.8.1, the workspace environment-variable filter did not block variables ending in `_ENDPOINT`, so an untrusted workspace `.env` file could set AZURE_SPEECH_ENDPOINT. Azure Speech preferred that value over the configured region, so when a synthesis or voice-list request was made, the attacker-selected endpoint received the operator&amp;#39;s Azure Speech key in the request header, allowing the key to be reused against the operator&amp;#39;s Azure Speech resource. Exploitation requires an operator to start OpenClaw in attacker-controlled workspace content with Azure Speech configured with a key and region and no trusted endpoint override set. The issue is fixed in 2026.8.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-5cqq-r556-6vv9</guid>
    </item>
  </channel>
</rss>
