VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

connect: vulnerability history, versions and safety

connect is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 26 releases, from Jul 2018 to 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
3 vulnerabilities recorded M2 L1
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 connect vulnerabilities

Vulert verdict on connect 3.7.0 i

Updated on 22 Oct 2026

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

Package health score 72/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 3.7.0 — unaffected i
  • Vulnerabilities on record 3 over 3 years · 0 in the last year i
  • Latest disclosure 05 May 2022 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Depended on by 23,845 packages i
  • Stars 9,872 i
  • OpenSSF scorecard 3/10 i
  • Last release 89 months 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 connect, 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
3.7.0 18 May 2019 none MIT — Details →
3.6.6 15 Feb 2018 none MIT — Details →
3.6.5 22 Sep 2017 none MIT — Details →
3.6.4 20 Sep 2017 none MIT — Details →
3.6.3 04 Aug 2017 none MIT — Details →
3.6.2 17 May 2017 none MIT — Details →
3.6.1 20 Apr 2017 none MIT — Details →
3.6.0 18 Feb 2017 none MIT — Details →
3.5.1 13 Feb 2017 none MIT — Details →
3.5.0 09 Sep 2016 none MIT — Details →
3.4.1 23 Jan 2016 none MIT — Details →
2.30.2 31 Jul 2015 none MIT — Details →
2.30.1 06 Jul 2015 none MIT — Details →
3.4.0 18 Jun 2015 none MIT — Details →
2.30.0 18 Jun 2015 none MIT — Details →
2.29.2 15 May 2015 none MIT — Details →
3.3.5 17 Mar 2015 none MIT — Details →
2.29.1 17 Mar 2015 none MIT — Details →
2.29.0 18 Feb 2015 none MIT — Details →
2.28.3 01 Feb 2015 none MIT — Details →
2.28.2 21 Jan 2015 none MIT — Details →
2.28.1 09 Jan 2015 none MIT — Details →
3.3.4 07 Jan 2015 none MIT — Details →
2.28.0 06 Jan 2015 none MIT — Details →
2.27.6 11 Dec 2014 none MIT — Details →
2.27.5 11 Dec 2014 none MIT — Details →
2.27.4 23 Nov 2014 none MIT — Details →
3.3.3 09 Nov 2014 none MIT — Details →
2.27.3 09 Nov 2014 none MIT — Details →
3.3.2 29 Oct 2014 none MIT — Details →
2.27.2 29 Oct 2014 none MIT — Details →
3.3.1 23 Oct 2014 none MIT — Details →
2.27.1 23 Oct 2014 none MIT — Details →
3.3.0 17 Oct 2014 none MIT — Details →
2.27.0 17 Oct 2014 none MIT — Details →
2.26.6 16 Oct 2014 none MIT — Details →
2.26.5 08 Oct 2014 none MIT — Details →
2.26.4 03 Oct 2014 none MIT — Details →
2.26.3 24 Sep 2014 none MIT — Details →
2.26.2 20 Sep 2014 none MIT — Details →
2.26.1 16 Sep 2014 none MIT — Details →
3.2.0 08 Sep 2014 none MIT — Details →
2.26.0 08 Sep 2014 none MIT — Details →
2.25.10 05 Sep 2014 none MIT — Details →
2.25.9 30 Aug 2014 none MIT — Details →
2.25.8 27 Aug 2014 none MIT — Details →
2.25.7 19 Aug 2014 none MIT — Details →
2.25.6 15 Aug 2014 none MIT — Details →
2.25.5 12 Aug 2014 none MIT — Details →
3.1.1 11 Aug 2014 none MIT — Details →
2.25.4 11 Aug 2014 none MIT — Details →
2.25.3 08 Aug 2014 none MIT — Details →
2.25.2 07 Aug 2014 none MIT — Details →
2.25.1 06 Aug 2014 none MIT — Details →
2.25.0 06 Aug 2014 none MIT — Details →
2.24.3 04 Aug 2014 none MIT — Details →
2.24.2 27 Jul 2014 none MIT — Details →
2.24.1 26 Jul 2014 none MIT — Details →
3.1.0 23 Jul 2014 none MIT — Details →
2.24.0 23 Jul 2014 none MIT — Details →
3.0.2 11 Jul 2014 none MIT — Details →
2.23.0 11 Jul 2014 none MIT — Details →
2.22.0 04 Jul 2014 none MIT — Details →
2.21.1 26 Jun 2014 none MIT — Details →
2.21.0 20 Jun 2014 none MIT — Details →
3.0.1 20 Jun 2014 none MIT — Details →
2.20.2 20 Jun 2014 none MIT — Details →
2.20.1 20 Jun 2014 none MIT — Details →
2.20.0 20 Jun 2014 none MIT — Details →
2.19.6 12 Jun 2014 none MIT — Details →
2.19.5 09 Jun 2014 none MIT — Details →
2.19.4 06 Jun 2014 none MIT — Details →
2.19.3 04 Jun 2014 none MIT — Details →
2.19.2 03 Jun 2014 none MIT — Details →
2.19.1 03 Jun 2014 none MIT — Details →
2.19.0 03 Jun 2014 none MIT — Details →
3.0.0 30 May 2014 none MIT — Details →
2.18.0 30 May 2014 none MIT — Details →
2.17.3 27 May 2014 none MIT — Details →
2.17.2 27 May 2014 none MIT — Details →
2.17.1 21 May 2014 none MIT — Details →
2.17.0 21 May 2014 none MIT — Details →
2.16.2 18 May 2014 none MIT — Details →
2.16.1 17 May 2014 none MIT — Details →
2.16.0 17 May 2014 none MIT — Details →
3.0.0-rc.2 05 May 2014 none MIT — Details →
2.15.0 05 May 2014 none MIT — Details →
2.14.5 24 Apr 2014 none MIT — Details →
2.14.4 07 Apr 2014 none MIT — Details →
2.14.3 18 Mar 2014 none MIT — Details →
2.14.2 12 Mar 2014 none MIT — Details →
3.0.0-rc.1 06 Mar 2014 none MIT — Details →
2.14.1 06 Mar 2014 none MIT — Details →
2.14.0 06 Mar 2014 none MIT — Details →
2.13.1 05 Mar 2014 M1 MIT Yes Details →
2.13.0 14 Feb 2014 M1 MIT Yes Details →
2.12.0 11 Dec 2013 M1 MIT Yes Details →
2.11.2 01 Dec 2013 M1 MIT Yes Details →
2.11.1 27 Nov 2013 M1 MIT Yes Details →
2.11.0 29 Oct 2013 M1 MIT Yes Details →
2.10.1 23 Oct 2013 M1 — Yes Details →
2.10.0 23 Oct 2013 M1 — Yes Details →
2.9.2 19 Oct 2013 M1 — Yes Details →
2.9.1 16 Oct 2013 M1 — Yes Details →
2.9.0 07 Sep 2013 M1 — Yes Details →
2.8.8 02 Sep 2013 M1 — Yes Details →
2.8.7 30 Aug 2013 M1 — Yes Details →
2.8.6 28 Aug 2013 M1 — Yes Details →
2.8.5 10 Aug 2013 M1 — Yes Details →
2.8.4 08 Jul 2013 M1 — Yes Details →
2.8.3 04 Jul 2013 M1 — Yes Details →
2.8.2 03 Jul 2013 M1 — Yes Details →
2.8.1 27 Jun 2013 M2 — Yes Details →
2.8.0 26 Jun 2013 M2 L1 — Yes Details →
2.7.11 03 Jun 2013 M2 L1 — Yes Details →
2.7.10 22 May 2013 M2 L1 — Yes Details →
2.7.9 07 May 2013 M2 L1 — Yes Details →
2.7.8 03 May 2013 M2 L1 — Yes Details →
2.7.7 30 Apr 2013 M2 L1 — Yes Details →
2.7.6 15 Apr 2013 M2 L1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2020 1
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for connect

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2013-7371: Node Connect Reflected Cross-Site Scripting in Sencha Labs Connect middleware 6.1 medium 2.8.2 05 May 2022
CVE-2018-3717: Cross-Site Scripting in connect 5.4 medium 2.14.0 26 Jul 2018
CVE-2013-7370: methodOverride Middleware Reflected Cross-Site Scripting in connect N/A low 2.8.1 31 Aug 2020

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 connect

Is connect safe to use?

Vulert records 3 vulnerabilities for connect in npm: 0 critical, 0 high, 2 medium and 1 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 connect's Vulert package health score?

Vulert scores connect 72/100, which reads as in good shape. 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 connect affected?

No. 3.7.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 connect should I use?

3.7.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 connect have?

3 vulnerabilities are recorded for connect in the npm ecosystem: 0 critical, 0 high, 2 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new connect vulnerabilities disclosed?

0 vulnerabilities were recorded for connect in the last 12 months, and the oldest entry in this database dates to 26 Jul 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 connect 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 connect for upcoming vulnerabilities?

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