<?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, 05 Oct 2026 01:54:04 +0000</lastBuildDate>
    <item>
      <title>BREW-cyclonedx-npm-CVE-2026-55849 — @cyclonedx/cyclonedx-npm: Shell Injection via Unsanitized `--workspace` Argument</title>
      <link>https://vulnerability.circl.lu/vuln/brew-cyclonedx-npm-cve-2026-55849</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: cyclonedx-npm&lt;/p&gt;
&lt;p&gt;@cyclonedx/cyclonedx-npm creates CycloneDX Software Bill of Materials from npm projects. From 2.1.0 before 5.0.0, the CLI passes user-supplied --workspace values to a subshell without proper sanitization when npm_execpath is unset or empty, allowing arbitrary OS command execution with the privileges of the invoking user. This issue is fixed in version 5.0.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: cyclonedx-npm&lt;/p&gt;
&lt;p&gt;@cyclonedx/cyclonedx-npm creates CycloneDX Software Bill of Materials from npm projects. From 2.1.0 before 5.0.0, the CLI passes user-supplied --workspace values to a subshell without proper sanitization when npm_execpath is unset or empty, allowing arbitrary OS command execution with the privileges of the invoking user. This issue is fixed in version 5.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/brew-cyclonedx-npm-cve-2026-55849</guid>
    </item>
    <item>
      <title>fkie_cve-2026-55849</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-55849</link>
      <description>&lt;p&gt;@cyclonedx/cyclonedx-npm creates CycloneDX Software Bill of Materials from npm projects. From 2.1.0 before 5.0.0, the CLI passes user-supplied --workspace values to a subshell without proper sanitization when npm_execpath is unset or empty, allowing arbitrary OS command execution with the privileges of the invoking user. This issue is fixed in version 5.0.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;@cyclonedx/cyclonedx-npm creates CycloneDX Software Bill of Materials from npm projects. From 2.1.0 before 5.0.0, the CLI passes user-supplied --workspace values to a subshell without proper sanitization when npm_execpath is unset or empty, allowing arbitrary OS command execution with the privileges of the invoking user. This issue is fixed in version 5.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-55849</guid>
    </item>
    <item>
      <title>GHSA-v75r-vx73-82pj — @cyclonedx/cyclonedx-npm: Shell Injection via Unsanitized --workspace Argument</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-v75r-vx73-82pj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @cyclonedx/cyclonedx-npm&lt;/p&gt;
&lt;p&gt;## Summary
A command injection vulnerability exists in `@cyclonedx/cyclonedx-npm` when the CLI is invoked with the `--workspace &amp;lt;value&amp;gt;` option while the environment variable `npm_execpath` is unset or empty.  
User‑supplied `--workspace` values are passed to a subshell without proper sanitization, enabling attackers to inject arbitrary OS commands.  
This issue corresponds to **CWE‑78**: Improper Neutralization of Special Elements used in an OS Command.&lt;/p&gt;
&lt;p&gt;The vulnerability was fixed in version [5.0.0][v5.0.0].&lt;/p&gt;
&lt;p&gt;## Vulnerability Details&lt;/p&gt;
&lt;p&gt;When `cyclonedx-npm` is executed with the `--workspace` option, the provided argument is incorporated into an internal shell command.  
If the environment variable `npm_execpath` is set, the tool uses the npm executable directly and no injection occurs.  
However, when `npm_execpath` is unset or empty, the tool falls back to spawning a subshell and interpolating the `--workspace` value directly into the command string without proper escaping or neutralization.&lt;/p&gt;
&lt;p&gt;As a result, specially crafted workspace names can break out of the intended command context and execute arbitrary commands with the privileges of the invoking user.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker who can influence the value passed to `--workspace` can execute arbitrary OS commands.  
This may lead to:&lt;/p&gt;
&lt;p&gt;* Arbitrary command execution
* Data exfiltration
* Local privilege escalation (depending on how the tool is used)
* Modification or destruction of files accessible to the user running the CLI…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @cyclonedx/cyclonedx-npm&lt;/p&gt;
&lt;p&gt;## Summary
A command injection vulnerability exists in `@cyclonedx/cyclonedx-npm` when the CLI is invoked with the `--workspace &amp;lt;value&amp;gt;` option while the environment variable `npm_execpath` is unset or empty.  
User‑supplied `--workspace` values are passed to a subshell without proper sanitization, enabling attackers to inject arbitrary OS commands.  
This issue corresponds to **CWE‑78**: Improper Neutralization of Special Elements used in an OS Command.&lt;/p&gt;
&lt;p&gt;The vulnerability was fixed in version [5.0.0][v5.0.0].&lt;/p&gt;
&lt;p&gt;## Vulnerability Details&lt;/p&gt;
&lt;p&gt;When `cyclonedx-npm` is executed with the `--workspace` option, the provided argument is incorporated into an internal shell command.  
If the environment variable `npm_execpath` is set, the tool uses the npm executable directly and no injection occurs.  
However, when `npm_execpath` is unset or empty, the tool falls back to spawning a subshell and interpolating the `--workspace` value directly into the command string without proper escaping or neutralization.&lt;/p&gt;
&lt;p&gt;As a result, specially crafted workspace names can break out of the intended command context and execute arbitrary commands with the privileges of the invoking user.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker who can influence the value passed to `--workspace` can execute arbitrary OS commands.  
This may lead to:&lt;/p&gt;
&lt;p&gt;* Arbitrary command execution
* Data exfiltration
* Local privilege escalation (depending on how the tool is used)
* Modification or destruction of files accessible to the user running the CLI…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-v75r-vx73-82pj</guid>
    </item>
  </channel>
</rss>
