debug vulnerabilities
Lightweight debugging utility for Node.js and the browser
- Registry
- npm
- Latest
- 4.4.3
- License
- MIT
4 known advisories
The latest version, 4.4.3, is not affected by any of them. Projects on older versions may be. Some versions were published with malicious code: remove them and rotate any secrets the install could read.
npm install debug@4.4.3Security advisories for debug
debug@4.4.2 contains malware after npm account takeover
- Affected
- >=4.4.2 <4.4.3
- Fixed in
- 4.4.3
Malicious code in a published version
- Affected
- 4.4.2
- Fixed in
- No fix released
debug Inefficient Regular Expression Complexity vulnerability
- Affected
- >=3.0.0 <3.1.0 · <2.6.9
- Fixed in
- 2.6.9, 3.1.0
Regular Expression Denial of Service in debug
- Affected
- <2.6.9 · >=3.0.0 <3.1.0 · >=3.2.0 <3.2.7 · >=4.0.0 <4.3.1
- Fixed in
- 2.6.9, 3.1.0, 3.2.7, 4.3.1
Which of your client projects still run an old debug?
NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other npm packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.