<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-01T19:41:56.418198+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2022-29244</id>
    <title>CVE-2022-29244 — npm packing does not respect root-level ignore files in workspaces</title>
    <updated>2026-10-01T19:41:56.421441+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm</p>
<p>npm pack ignores root-level .gitignore and .npmignore file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=&lt;name&gt;`). Anyone who has run `npm pack` or `npm publish` inside a workspace, as of v7.9.0 and v7.13.0 respectively, may be affected and have published files into the npm registry they did not intend to include. Users should upgrade to the latest, patched version of npm v8.11.0, run: npm i -g npm@latest . Node.js versions v16.15.1, v17.19.1, and v18.3.0 include the patched v8.11.0 version of npm.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-29244"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-hj9c-8jmm-8c52</id>
    <title>GHSA-hj9c-8jmm-8c52 — Packing does not respect root-level ignore files in workspaces</title>
    <updated>2026-10-01T19:41:56.421609+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: npm</p>
<p>### Impact
`npm pack` ignores root-level `.gitignore` &amp; `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=&lt;name&gt;`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) &amp; [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include.</p>
<p>### Patch
- Upgrade to the latest, patched version of `npm` ([`v8.11.0`](https://github.com/npm/cli/releases/tag/v8.11.0) or greater), run: `npm i -g npm@latest`
- Node.js versions [`v16.15.1`](https://github.com/nodejs/node/releases/tag/v16.15.1), [`v17.19.1`](https://github.com/nodejs/node/releases/tag/v17.9.1) &amp; [`v18.3.0`](https://github.com/nodejs/node/releases/tag/v18.3.0) include the patched `v8.11.0` version of `npm`</p>
<p>#### Steps to take to see if you're impacted
1. Run `npm publish --dry-run` or `npm pack` with an `npm` version `&gt;=7.9.0` &amp; `&lt;8.11.0` inside the project's root directory using a workspace flag like: `--workspaces` or `--workspace=&lt;name&gt;` (ex. `npm pack --workspace=foo`)
2. Check the output in your terminal which will list the package contents (note: `tar -tvf &lt;package-on-disk&gt;` also works)
3. If you find that there are files included you did not expect, you should:
  3.1. Create &amp; publish a new release excluding those files (ref. ["Keeping files out of your Package"](https://d…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-hj9c-8jmm-8c52"/>
  </entry>
</feed>
