VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

node-inspector: vulnerability history, versions and safety

node-inspector is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 0 release, first recorded in May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all node-inspector vulnerabilities

Vulert verdict on node-inspector 1.1.2 i

Updated on 23 Oct 2026

Good news: 1.1.2, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 59/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Widely used
  • Community Quiet

What to do: Stay on 1.1.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.1.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.1.2 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 13 May 2022 i
  • Highest CVSS 8.8 i
  • With no published fix 1 i
  • Depended on by 21 packages i
  • Stars 12,636 i
  • OpenSSF scorecard 1/10 i
  • Last release 104 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for node-inspector, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.1.2 31 Jan 2018 none — — Details →
1.1.1 24 Apr 2017 none — — Details →
1.1.0 12 Apr 2017 none — — Details →
1.0.1 10 Apr 2017 none — — Details →
1.0.0 28 Mar 2017 none — — Details →
0.12.10 06 Mar 2017 none — — Details →
0.7.5 21 Dec 2016 none — — Details →
0.12.8 08 Apr 2016 none — — Details →
0.12.7 25 Feb 2016 none — — Details →
0.12.6 09 Feb 2016 none — — Details →
0.12.5 06 Dec 2015 none — — Details →
0.12.4 03 Dec 2015 none — — Details →
0.12.3 05 Sep 2015 none — — Details →
0.12.2 05 Aug 2015 none — — Details →
0.12.1 29 Jul 2015 none — — Details →
0.12.0 29 Jul 2015 none — — Details →
0.11.2 23 Jul 2015 none — — Details →
0.11.1 30 Jun 2015 none — — Details →
0.11.0 29 Jun 2015 none — — Details →
0.10.2 14 Jun 2015 none — — Details →
0.10.1 13 May 2015 none — — Details →
0.10.0 24 Apr 2015 none — — Details →
0.9.2 10 Mar 2015 none — — Details →
0.9.1 23 Feb 2015 none — — Details →
0.9.0 20 Feb 2015 none — — Details →
0.8.3 12 Jan 2015 none — — Details →
0.8.1 08 Dec 2014 none — — Details →
0.8.0 04 Dec 2014 none — — Details →
0.7.4 05 Jun 2014 none — — Details →
0.7.3 08 Apr 2014 none — — Details →
0.7.2 21 Mar 2014 none — — Details →
0.7.1 11 Mar 2014 none — — Details →
0.7.0 20 Feb 2014 none — — Details →
0.2.0-beta1 23 Jan 2014 none — — Details →
0.2.0-beta2 23 Jan 2014 none — — Details →
0.2.0-beta3 23 Jan 2014 none — — Details →
0.2.0-beta4 23 Jan 2014 none — — Details →
0.3.0-preview1 23 Jan 2014 none — — Details →
0.7.0-2 23 Jan 2014 none — — Details →
0.7.0-1 26 Dec 2013 none — — Details →
0.6.2 04 Dec 2013 none — — Details →
0.6.1 17 Nov 2013 none — — Details →
0.6.0 12 Nov 2013 none — — Details →
0.5.0 20 Sep 2013 none — — Details →
0.4.0 05 Sep 2013 none — — Details →
0.3.4 21 Aug 2013 none — — Details →
0.3.3 12 Aug 2013 none — — Details →
0.3.2 22 Jul 2013 none — — Details →
0.3.1 15 Jul 2013 none — — Details →
0.3.0 15 Jul 2013 none — — Details →
0.1.10 03 Sep 2011 none — — Details →
0.1.9 15 Aug 2011 none — — Details →
0.1.8 24 Jul 2011 none — — Details →
0.0.1 14 Jul 2011 none — — Details →
0.0.2 14 Jul 2011 none — — Details →
0.0.3 14 Jul 2011 none — — Details →
0.0.4 14 Jul 2011 none — — Details →
0.1.0 14 Jul 2011 none — — Details →
0.1.1 14 Jul 2011 none — — Details →
0.1.2 14 Jul 2011 none — — Details →
0.1.3 14 Jul 2011 none — — Details →
0.1.4 14 Jul 2011 none — — Details →
0.1.5 14 Jul 2011 none — — Details →
0.1.6 14 Jul 2011 none — — Details →
0.1.7 14 Jul 2011 none — — Details →

All 65 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for node-inspector

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-7160: Node.js Inspector RCE via DNS Rebinding in node-inspector 8.8 high No fix published 13 May 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About node-inspector

Is node-inspector safe to use?

Vulert records 1 vulnerabilities for node-inspector in npm: 0 critical, 1 high, 0 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is node-inspector's Vulert package health score?

Vulert scores node-inspector 59/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of node-inspector affected?

No. 1.1.2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of node-inspector should I use?

1.1.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does node-inspector have?

1 vulnerability is recorded for node-inspector in the npm ecosystem: 0 critical, 1 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new node-inspector vulnerabilities disclosed?

0 vulnerabilities were recorded for node-inspector in the last 12 months, and the oldest entry in this database dates to 13 May 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of node-inspector are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor node-inspector for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the node-inspector version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.