<?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://db.gcve.eu</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, 16 Oct 2026 19:37:17 +0000</lastBuildDate>
    <item>
      <title>GHSA-9ppg-jx86-fqw7 — Unauthorized npm publish of cline@2.3.0 with modified postinstall script</title>
      <link>https://db.gcve.eu/vuln/ghsa-9ppg-jx86-fqw7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: cline&lt;/p&gt;
&lt;p&gt;### Description
On February 17, 2026 at 3:26 AM PT, an unauthorized party used a compromised npm publish token to publish an update to Cline CLI on the NPM registry: cline@2.3.0. The published package contains a modified package.json with an added postinstall script:
`&amp;#34;postinstall&amp;#34;: &amp;#34;npm install -g openclaw@latest&amp;#34;`
This causes openclaw (an unrelated, non-malicious open source package) to be globally installed when cline@2.3.0 is installed. No other files were modified -- the CLI binary (dist/cli.mjs) and all other package contents are identical to the legitimate cline@2.2.3 release.
A corrected version (2.4.0) was published at 11:23 AM PT and 2.3.0 was deprecated at 11:30 AM PT. The compromised token has been revoked and npm publishing now uses OIDC provenance via GitHub Actions.&lt;/p&gt;
&lt;p&gt;### Impact
Users who installed Cline CLI cline@2.3.0 during the approximately 8-hour window between 3:26 AM PT and 11:30 AM PT on February 17 will have openclaw globally installed. The openclaw package is a legitimate open source project and is not malicious, but its installation was not authorized or intended.&lt;/p&gt;
&lt;p&gt;The Cline VS Code extension and JetBrains plugin were not affected. This advisory applies only to the Cline CLI package published on npm.&lt;/p&gt;
&lt;p&gt;### Patches
Versions 2.4.0 and higher are fixed&lt;/p&gt;
&lt;p&gt;### Workarounds
If you installed Cline CLI cline@2.3.0:
1. Update to the latest version of the Cline CLI
`cline update` or `npm installl -g cline@latest`
2. Verify that you have a fixed version (2.4.0 or…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: cline&lt;/p&gt;
&lt;p&gt;### Description
On February 17, 2026 at 3:26 AM PT, an unauthorized party used a compromised npm publish token to publish an update to Cline CLI on the NPM registry: cline@2.3.0. The published package contains a modified package.json with an added postinstall script:
`&amp;#34;postinstall&amp;#34;: &amp;#34;npm install -g openclaw@latest&amp;#34;`
This causes openclaw (an unrelated, non-malicious open source package) to be globally installed when cline@2.3.0 is installed. No other files were modified -- the CLI binary (dist/cli.mjs) and all other package contents are identical to the legitimate cline@2.2.3 release.
A corrected version (2.4.0) was published at 11:23 AM PT and 2.3.0 was deprecated at 11:30 AM PT. The compromised token has been revoked and npm publishing now uses OIDC provenance via GitHub Actions.&lt;/p&gt;
&lt;p&gt;### Impact
Users who installed Cline CLI cline@2.3.0 during the approximately 8-hour window between 3:26 AM PT and 11:30 AM PT on February 17 will have openclaw globally installed. The openclaw package is a legitimate open source project and is not malicious, but its installation was not authorized or intended.&lt;/p&gt;
&lt;p&gt;The Cline VS Code extension and JetBrains plugin were not affected. This advisory applies only to the Cline CLI package published on npm.&lt;/p&gt;
&lt;p&gt;### Patches
Versions 2.4.0 and higher are fixed&lt;/p&gt;
&lt;p&gt;### Workarounds
If you installed Cline CLI cline@2.3.0:
1. Update to the latest version of the Cline CLI
`cline update` or `npm installl -g cline@latest`
2. Verify that you have a fixed version (2.4.0 or…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-9ppg-jx86-fqw7</guid>
    </item>
    <item>
      <title>MAL-2026-1380 — Malicious code in cline (npm)</title>
      <link>https://db.gcve.eu/vuln/mal-2026-1380</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: cline&lt;/p&gt;
&lt;p&gt;---
_-= Per source details. Do not edit below this line.=-_&lt;/p&gt;
&lt;p&gt;## Source: amazon-inspector (38d7531f4d4af07fee607e1d2985d0ea5b41dbf28cca5bc16c8457934e372f86)
The package cline was found to contain malicious code.&lt;/p&gt;
&lt;p&gt;## Source: ghsa-malware (3c16746b2d863d4c24bbc2297611c642a02942b47d12b675c4a3120911c72eec)
### Description
On February 17, 2026 at 3:26 AM PT, an unauthorized party used a compromised npm publish token to publish an update to Cline CLI on the NPM registry: cline@2.3.0. The published package contains a modified package.json with an added postinstall script:
`&amp;#34;postinstall&amp;#34;: &amp;#34;npm install -g openclaw@latest&amp;#34;`
This causes openclaw (an unrelated, non-malicious open source package) to be globally installed when cline@2.3.0 is installed. No other files were modified -- the CLI binary (dist/cli.mjs) and all other package contents are identical to the legitimate cline@2.2.3 release.
A corrected version (2.4.0) was published at 11:23 AM PT and 2.3.0 was deprecated at 11:30 AM PT. The compromised token has been revoked and npm publishing now uses OIDC provenance via GitHub Actions.&lt;/p&gt;
&lt;p&gt;### Impact
Users who installed Cline CLI cline@2.3.0 during the approximately 8-hour window between 3:26 AM PT and 11:30 AM PT on February 17 will have openclaw globally installed. The openclaw package is a legitimate open source project and is not malicious, but its installation was not authorized or intended.&lt;/p&gt;
&lt;p&gt;The Cline VS Code extension and JetBrains plugin were not affected. This advisory applies…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: cline&lt;/p&gt;
&lt;p&gt;---
_-= Per source details. Do not edit below this line.=-_&lt;/p&gt;
&lt;p&gt;## Source: amazon-inspector (38d7531f4d4af07fee607e1d2985d0ea5b41dbf28cca5bc16c8457934e372f86)
The package cline was found to contain malicious code.&lt;/p&gt;
&lt;p&gt;## Source: ghsa-malware (3c16746b2d863d4c24bbc2297611c642a02942b47d12b675c4a3120911c72eec)
### Description
On February 17, 2026 at 3:26 AM PT, an unauthorized party used a compromised npm publish token to publish an update to Cline CLI on the NPM registry: cline@2.3.0. The published package contains a modified package.json with an added postinstall script:
`&amp;#34;postinstall&amp;#34;: &amp;#34;npm install -g openclaw@latest&amp;#34;`
This causes openclaw (an unrelated, non-malicious open source package) to be globally installed when cline@2.3.0 is installed. No other files were modified -- the CLI binary (dist/cli.mjs) and all other package contents are identical to the legitimate cline@2.2.3 release.
A corrected version (2.4.0) was published at 11:23 AM PT and 2.3.0 was deprecated at 11:30 AM PT. The compromised token has been revoked and npm publishing now uses OIDC provenance via GitHub Actions.&lt;/p&gt;
&lt;p&gt;### Impact
Users who installed Cline CLI cline@2.3.0 during the approximately 8-hour window between 3:26 AM PT and 11:30 AM PT on February 17 will have openclaw globally installed. The openclaw package is a legitimate open source project and is not malicious, but its installation was not authorized or intended.&lt;/p&gt;
&lt;p&gt;The Cline VS Code extension and JetBrains plugin were not affected. This advisory applies…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/mal-2026-1380</guid>
    </item>
  </channel>
</rss>
