<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-10T17:30:53.118379+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2016-3956</id>
    <title>CVE-2016-3956</title>
    <updated>2026-11-10T17:30:53.120934+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>The CLI in npm before 2.15.1 and 3.x before 3.8.3, as used in Node.js 0.10 before 0.10.44, 0.12 before 0.12.13, 4 before 4.4.2, and 5 before 5.10.0, includes bearer tokens with arbitrary requests, which allows remote HTTP servers to obtain sensitive information by reading Authorization headers.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2016-3956"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-m5h6-hr3q-22h5</id>
    <title>GHSA-m5h6-hr3q-22h5 — npm Token Leak in npm</title>
    <updated>2026-11-10T17:30:53.120982+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: npm</p>
<p>Affected versions of the `npm` package include the bearer token of the logged in user in every request made by the CLI, even if the request is not directed towards the user's active registry.</p>
<p>An attacker could create an HTTP server to collect tokens, and by various means including but not limited to install scripts, cause the npm CLI to make a request to that server, which would compromise the user's token.</p>
<p>This compromised token could be used to do anything that the user could do, including publishing new packages.</p>
<p>## Recommendation</p>
<p>1. Update npm with `npm install npm@latest -g`
2. [Revoke your Tokens](https://www.npmjs.com/settings/tokens)
3. Enable [Two-Factor Authentication](https://docs.npmjs.com/getting-started/using-two-factor-authentication)</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-m5h6-hr3q-22h5"/>
  </entry>
</feed>
