VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

restify: vulnerability history, versions and safety

restify is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 38 releases, first recorded in Nov 2018. 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 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

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 restify vulnerabilities

Vulert verdict on restify 12.0.0 i

Updated on 23 Oct 2026

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

Package health score 86/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 12.0.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 09 Nov 2018 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Depended on by 94 packages i
  • Stars 10,689 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month ago i
  • Licence MIT 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 restify, 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
12.0.0 25 Aug 2026 none MIT — Details →
12.0.0-rc.0 18 Aug 2026 none MIT — Details →
9.1.0 13 Jun 2023 none MIT — Details →
11.1.0 24 Feb 2023 none MIT — Details →
11.0.0 17 Jan 2023 none MIT — Details →
10.0.0 29 Nov 2022 none MIT — Details →
9.0.0 15 Nov 2022 none MIT — Details →
9.0.0-rc.3 06 May 2022 none MIT — Details →
9.0.0-rc.2 24 Mar 2022 none MIT — Details →
9.0.0-rc.1 11 Feb 2022 none MIT — Details →
8.6.1 10 Feb 2022 none MIT — Details →
8.6.0 29 Sep 2021 none MIT — Details →
8.5.1 13 Dec 2019 none MIT — Details →
8.5.0 02 Dec 2019 none MIT — Details →
8.4.1 27 Nov 2019 none MIT — Details →
8.4.0 31 Jul 2019 none MIT — Details →
8.3.3 04 Jun 2019 none MIT — Details →
8.3.2 06 May 2019 none MIT — Details →
8.3.1 25 Apr 2019 none MIT — Details →
8.3.0 11 Apr 2019 none MIT — Details →
8.2.0 18 Mar 2019 none MIT — Details →
8.1.1 14 Mar 2019 none MIT — Details →
8.1.0 07 Mar 2019 none MIT — Details →
8.0.0 20 Feb 2019 none MIT — Details →
7.7.0 01 Feb 2019 none MIT — Details →
7.6.0 19 Jan 2019 none MIT — Details →
7.5.0 10 Jan 2019 none MIT — Details →
7.4.0 02 Jan 2019 none MIT — Details →
7.3.0 07 Dec 2018 none MIT — Details →
7.2.3 16 Nov 2018 none MIT — Details →
7.2.2 30 Oct 2018 none MIT — Details →
7.2.1 07 Jun 2018 none MIT — Details →
4.3.4 24 May 2018 none MIT — Details →
7.2.0 16 May 2018 none MIT — Details →
7.1.2 15 May 2018 none MIT — Details →
7.1.1 10 Apr 2018 none MIT — Details →
4.3.3 07 Apr 2018 none MIT — Details →
7.1.0 26 Mar 2018 none MIT — Details →
7.0.0 20 Mar 2018 none MIT — Details →
6.4.0 20 Mar 2018 none MIT — Details →
4.3.2 21 Nov 2017 none MIT — Details →
6.3.4 21 Nov 2017 none MIT — Details →
6.3.3 20 Nov 2017 none MIT — Details →
5.2.1 20 Nov 2017 none MIT — Details →
6.3.2 08 Nov 2017 none MIT — Details →
6.3.1 03 Nov 2017 none MIT — Details →
6.3.0 02 Nov 2017 none MIT — Details →
6.2.3 18 Oct 2017 none MIT — Details →
6.2.2 18 Oct 2017 none MIT — Details →
6.2.1 18 Oct 2017 none MIT — Details →
6.2.0 16 Oct 2017 none MIT — Details →
6.0.1 19 Sep 2017 none MIT — Details →
6.0.0 15 Sep 2017 none MIT — Details →
5.2.0 17 Aug 2017 none MIT — Details →
5.1.0 10 Aug 2017 none MIT — Details →
5.0.1 18 Jul 2017 none MIT — Details →
4.3.1 28 Jun 2017 none MIT — Details →
5.0.0 27 Jun 2017 none MIT — Details →
5.0.0-beta-8.0 19 Apr 2017 none MIT — Details →
5.0.0-beta-7.0 09 Mar 2017 none MIT — Details →
5.0.0-beta-6.0 03 Mar 2017 none MIT — Details →
5.0.0-beta-5.0 28 Feb 2017 none MIT — Details →
5.0.0-beta-4.0 22 Dec 2016 none MIT — Details →
5.0.0-beta-3.0 16 Dec 2016 none MIT — Details →
4.3.0 14 Nov 2016 none MIT — Details →
4.2.0 26 Oct 2016 none MIT — Details →
5.0.0-beta-2 16 Sep 2016 none MIT — Details →
5.0.0-beta-1 13 Sep 2016 none MIT — Details →
4.1.1 16 Jun 2016 none MIT — Details →
4.1.0 23 May 2016 none MIT — Details →
4.0.4 10 Feb 2016 M1 MIT Yes Details →
4.0.3 18 Sep 2015 M1 MIT Yes Details →
4.0.2 09 Sep 2015 M1 MIT Yes Details →
4.0.0 14 Aug 2015 M1 MIT Yes Details →
3.0.3 19 May 2015 M1 MIT Yes Details →
3.0.2 11 Apr 2015 M1 MIT Yes Details →
3.0.1 17 Mar 2015 M1 MIT Yes Details →
3.0.0 11 Mar 2015 M1 MIT Yes Details →
2.8.5 23 Jan 2015 M1 MIT Yes Details →
2.8.4 12 Dec 2014 M1 MIT Yes Details →
2.8.3 02 Oct 2014 M1 MIT Yes Details →
2.8.2 06 Aug 2014 M1 MIT Yes Details →
2.8.1 16 May 2014 M1 MIT Yes Details →
2.8.0 13 May 2014 M1 MIT Yes Details →
2.7.0 26 Mar 2014 M1 MIT Yes Details →
2.6.3 04 Mar 2014 M1 MIT Yes Details →
2.6.2 26 Feb 2014 M1 MIT Yes Details →
2.6.1 09 Dec 2013 M1 MIT Yes Details →
2.6.0 14 Jun 2013 M1 MIT Yes Details →
2.5.1 21 May 2013 M1 MIT Yes Details →
2.5.0 07 May 2013 M1 MIT Yes Details →
2.4.1 11 Apr 2013 M1 MIT Yes Details →
2.4.0 10 Apr 2013 M1 MIT Yes Details →
2.3.5 26 Mar 2013 M1 MIT Yes Details →
2.3.4 08 Mar 2013 M1 MIT Yes Details →
2.3.3 05 Mar 2013 M1 MIT Yes Details →
2.3.2 02 Mar 2013 M1 MIT Yes Details →
2.3.1 28 Feb 2013 M1 MIT Yes Details →
2.3.0 28 Feb 2013 M1 MIT Yes Details →
2.2.1 11 Feb 2013 M1 MIT Yes Details →
2.2.0 11 Feb 2013 M1 — Yes Details →
2.1.1 30 Jan 2013 M1 — Yes Details →
2.1.0 30 Jan 2013 M1 — Yes Details →
2.0.4 04 Jan 2013 M1 — Yes Details →
2.0.3 03 Jan 2013 M1 — Yes Details →
2.0.2 03 Jan 2013 M1 — Yes Details →
2.0.1 01 Jan 2013 M1 — Yes Details →
2.0.0 30 Dec 2012 M1 — Yes Details →
1.4.4 20 Jul 2012 none — — Details →
1.4.3 15 Jun 2012 none — — Details →
1.4.2 14 May 2012 none — — Details →
1.4.1 23 Apr 2012 none — — Details →
1.4.0 11 Apr 2012 none — — Details →
1.3.0 12 Mar 2012 none — — Details →
1.2.0 08 Mar 2012 none — — Details →
1.1.1 05 Mar 2012 none — — Details →
1.1.0 29 Feb 2012 none — — Details →
1.0.1 20 Feb 2012 none — — Details →
1.0.0 13 Feb 2012 none — — Details →
0.5.7 08 Feb 2012 none — — Details →

The newest 120 of 186 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 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 restify

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-16018: Cross-Site Scripting (XSS) in restify 6.1 medium 4.1.0 09 Nov 2018

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 restify

Is restify safe to use?

Vulert records 1 vulnerabilities for restify in npm: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is restify's Vulert package health score?

Vulert scores restify 86/100, which reads as healthy. 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 restify affected?

No. 12.0.0, 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 restify should I use?

12.0.0 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 restify have?

1 vulnerability is recorded for restify in the npm ecosystem: 0 critical, 0 high, 1 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 restify vulnerabilities disclosed?

0 vulnerabilities were recorded for restify in the last 12 months, and the oldest entry in this database dates to 09 Nov 2018. 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 restify 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 restify for upcoming vulnerabilities?

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