<?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>Fri, 02 Oct 2026 13:37:35 +0000</lastBuildDate>
    <item>
      <title>BREW-openclaw-cli-CVE-2026-35641 — OpenClaw has an Arbitrary Malicious Code Execution Vulnerability</title>
      <link>https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-35641</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: openclaw-cli&lt;/p&gt;
&lt;p&gt;&amp;gt; Fixed in OpenClaw 2026.3.24, the current shipping release.&lt;/p&gt;
&lt;p&gt;### Summary
During the installation phase of OpenClaw local plugins/hooks, the Git executable can be hijacked by a project-level .npmrc file, leading to arbitrary code execution during installation.&lt;/p&gt;
&lt;p&gt;### Details
Please note that the source code locations mentioned below are based on version openclaw-2026.3.13-1, but the issue has been confirmed to still exist in the current latest version, 2026.3.23.&lt;/p&gt;
&lt;p&gt;When installing a local plugin directory, local plugin archive, local hook pack directory, or local hook pack archive, OpenClaw first copies the source directory to a temporary `stageDir`, then executes the following in that directory:&lt;/p&gt;
&lt;p&gt;```
npm install --omit=dev --silent --ignore-scripts
```&lt;/p&gt;
&lt;p&gt;See `src/infra/install-package-dir.ts:176-199`.&lt;/p&gt;
&lt;p&gt;Since this process does not strip the project root `.npmrc`, and npm reads the project-level `.npmrc` during local project installation, an attacker could use a `.npmrc` file in a malicious plugin or hook directory to override npm’s `git` executable path. By leveraging a Git dependency, the attacker could trigger npm to call this malicious program, thereby executing arbitrary local code during the installation phase.&lt;/p&gt;
&lt;p&gt;**Affected Paths**&lt;/p&gt;
&lt;p&gt;- Plugin CLI entry point: `src/cli/plugins-cli.ts:199-255`
- Hook CLI entry point: `src/cli/hooks-cli.ts:573-676`
- Plugin local directory / archive installation: `src/plugins/install.ts:379-405`, `src/plugins/install.ts:541-565`
- Hook local dir…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: openclaw-cli&lt;/p&gt;
&lt;p&gt;&amp;gt; Fixed in OpenClaw 2026.3.24, the current shipping release.&lt;/p&gt;
&lt;p&gt;### Summary
During the installation phase of OpenClaw local plugins/hooks, the Git executable can be hijacked by a project-level .npmrc file, leading to arbitrary code execution during installation.&lt;/p&gt;
&lt;p&gt;### Details
Please note that the source code locations mentioned below are based on version openclaw-2026.3.13-1, but the issue has been confirmed to still exist in the current latest version, 2026.3.23.&lt;/p&gt;
&lt;p&gt;When installing a local plugin directory, local plugin archive, local hook pack directory, or local hook pack archive, OpenClaw first copies the source directory to a temporary `stageDir`, then executes the following in that directory:&lt;/p&gt;
&lt;p&gt;```
npm install --omit=dev --silent --ignore-scripts
```&lt;/p&gt;
&lt;p&gt;See `src/infra/install-package-dir.ts:176-199`.&lt;/p&gt;
&lt;p&gt;Since this process does not strip the project root `.npmrc`, and npm reads the project-level `.npmrc` during local project installation, an attacker could use a `.npmrc` file in a malicious plugin or hook directory to override npm’s `git` executable path. By leveraging a Git dependency, the attacker could trigger npm to call this malicious program, thereby executing arbitrary local code during the installation phase.&lt;/p&gt;
&lt;p&gt;**Affected Paths**&lt;/p&gt;
&lt;p&gt;- Plugin CLI entry point: `src/cli/plugins-cli.ts:199-255`
- Hook CLI entry point: `src/cli/hooks-cli.ts:573-676`
- Plugin local directory / archive installation: `src/plugins/install.ts:379-405`, `src/plugins/install.ts:541-565`
- Hook local dir…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-35641</guid>
    </item>
    <item>
      <title>EUVD-2026-329518</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-329518</link>
      <description>EUVD-2026-329518</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-329518</guid>
    </item>
    <item>
      <title>fkie_cve-2026-35641</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-35641</link>
      <description>&lt;p&gt;OpenClaw before 2026.3.24 contains an arbitrary code execution vulnerability in local plugin and hook installation that allows attackers to execute malicious code by crafting a .npmrc file with a git executable override. During npm install execution in the staged package directory, attackers can leverage git dependencies to trigger execution of arbitrary programs specified in the attacker-controlled .npmrc configuration file.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenClaw before 2026.3.24 contains an arbitrary code execution vulnerability in local plugin and hook installation that allows attackers to execute malicious code by crafting a .npmrc file with a git executable override. During npm install execution in the staged package directory, attackers can leverage git dependencies to trigger execution of arbitrary programs specified in the attacker-controlled .npmrc configuration file.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-35641</guid>
    </item>
    <item>
      <title>GHSA-m3mh-3mpg-37hw — OpenClaw has an Arbitrary Malicious Code Execution Vulnerability</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m3mh-3mpg-37hw</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: openclaw&lt;/p&gt;
&lt;p&gt;&amp;gt; Fixed in OpenClaw 2026.3.24, the current shipping release.&lt;/p&gt;
&lt;p&gt;### Summary
During the installation phase of OpenClaw local plugins/hooks, the Git executable can be hijacked by a project-level .npmrc file, leading to arbitrary code execution during installation.&lt;/p&gt;
&lt;p&gt;### Details
Please note that the source code locations mentioned below are based on version openclaw-2026.3.13-1, but the issue has been confirmed to still exist in the current latest version, 2026.3.23.&lt;/p&gt;
&lt;p&gt;When installing a local plugin directory, local plugin archive, local hook pack directory, or local hook pack archive, OpenClaw first copies the source directory to a temporary `stageDir`, then executes the following in that directory:&lt;/p&gt;
&lt;p&gt;```
npm install --omit=dev --silent --ignore-scripts
```&lt;/p&gt;
&lt;p&gt;See `src/infra/install-package-dir.ts:176-199`.&lt;/p&gt;
&lt;p&gt;Since this process does not strip the project root `.npmrc`, and npm reads the project-level `.npmrc` during local project installation, an attacker could use a `.npmrc` file in a malicious plugin or hook directory to override npm’s `git` executable path. By leveraging a Git dependency, the attacker could trigger npm to call this malicious program, thereby executing arbitrary local code during the installation phase.&lt;/p&gt;
&lt;p&gt;**Affected Paths**&lt;/p&gt;
&lt;p&gt;- Plugin CLI entry point: `src/cli/plugins-cli.ts:199-255`
- Hook CLI entry point: `src/cli/hooks-cli.ts:573-676`
- Plugin local directory / archive installation: `src/plugins/install.ts:379-405`, `src/plugins/install.ts:541-565`
- Hook local dir…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: openclaw&lt;/p&gt;
&lt;p&gt;&amp;gt; Fixed in OpenClaw 2026.3.24, the current shipping release.&lt;/p&gt;
&lt;p&gt;### Summary
During the installation phase of OpenClaw local plugins/hooks, the Git executable can be hijacked by a project-level .npmrc file, leading to arbitrary code execution during installation.&lt;/p&gt;
&lt;p&gt;### Details
Please note that the source code locations mentioned below are based on version openclaw-2026.3.13-1, but the issue has been confirmed to still exist in the current latest version, 2026.3.23.&lt;/p&gt;
&lt;p&gt;When installing a local plugin directory, local plugin archive, local hook pack directory, or local hook pack archive, OpenClaw first copies the source directory to a temporary `stageDir`, then executes the following in that directory:&lt;/p&gt;
&lt;p&gt;```
npm install --omit=dev --silent --ignore-scripts
```&lt;/p&gt;
&lt;p&gt;See `src/infra/install-package-dir.ts:176-199`.&lt;/p&gt;
&lt;p&gt;Since this process does not strip the project root `.npmrc`, and npm reads the project-level `.npmrc` during local project installation, an attacker could use a `.npmrc` file in a malicious plugin or hook directory to override npm’s `git` executable path. By leveraging a Git dependency, the attacker could trigger npm to call this malicious program, thereby executing arbitrary local code during the installation phase.&lt;/p&gt;
&lt;p&gt;**Affected Paths**&lt;/p&gt;
&lt;p&gt;- Plugin CLI entry point: `src/cli/plugins-cli.ts:199-255`
- Hook CLI entry point: `src/cli/hooks-cli.ts:573-676`
- Plugin local directory / archive installation: `src/plugins/install.ts:379-405`, `src/plugins/install.ts:541-565`
- Hook local dir…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m3mh-3mpg-37hw</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1065 — OpenClaw: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1065</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um Administratorrechte zu erlangen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten offenzulegen oder zu manipulieren oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um Administratorrechte zu erlangen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten offenzulegen oder zu manipulieren oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1065</guid>
    </item>
  </channel>
</rss>
