VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

velocityjs: vulnerability history, versions and safety

velocityjs is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 86 releases, from May 2026 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 H1
i
1 with no fix published

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

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

Most recent disclosure 24 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all velocityjs vulnerabilities

Vulert verdict on velocityjs 2.1.7 i

Updated on 23 Oct 2026

Careful: 2.1.7 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

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

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.1.7 — affected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 24 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Depended on by 118 packages i
  • Stars 615 i
  • OpenSSF scorecard 3/10 i
  • Last release 3 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 velocityjs, 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
2.1.7 19 Jul 2026 H1 MIT No Details →
2.1.6 06 May 2026 C1 H1 MIT No Details →
2.1.5 23 Apr 2025 C1 H1 MIT No Details →
2.1.4 23 Apr 2025 C1 H1 MIT No Details →
2.1.3 14 Apr 2025 C1 H1 MIT No Details →
2.1.2 14 Apr 2025 C1 H1 MIT No Details →
2.1.1 13 Apr 2025 C1 H1 MIT No Details →
2.1.0 13 Apr 2025 C1 H1 MIT No Details →
3.0.0-beta1 19 Sep 2024 H1 MIT No Details →
3.0.0-beta 19 Sep 2024 H1 MIT No Details →
2.1.0-beta 14 Feb 2023 C1 H1 MIT No Details →
2.0.6 16 Jan 2022 C1 H1 MIT No Details →
2.0.5 12 Nov 2021 C1 H1 MIT No Details →
2.0.5-beta 09 Nov 2021 C1 H1 MIT No Details →
2.0.4 27 Oct 2021 C1 H1 MIT No Details →
2.0.3 02 Dec 2020 C1 H1 MIT No Details →
2.0.2 19 Oct 2020 C1 H1 MIT No Details →
2.0.1 02 Sep 2020 C1 H1 MIT No Details →
2.0.0 26 Sep 2019 C1 H1 MIT No Details →
1.1.5 18 Sep 2019 C1 H1 MIT No Details →
1.1.4 27 Aug 2019 C1 H1 MIT No Details →
1.1.3 17 Sep 2018 C1 H1 MIT No Details →
1.1.2 08 Aug 2018 C1 H1 MIT No Details →
1.1.1 14 Jun 2018 C1 H1 MIT No Details →
1.1.0 12 Jun 2018 C1 H1 MIT No Details →
1.0.2 06 Jun 2018 C1 H1 MIT No Details →
1.0.2-beta 06 Jun 2018 C1 H1 MIT No Details →
1.0.1 08 Mar 2018 C1 H1 MIT No Details →
1.0.0 13 Jan 2018 C1 H1 MIT No Details →
0.10.1 10 Nov 2017 C1 H1 MIT No Details →
0.10.0 07 Nov 2017 C1 H1 MIT No Details →
0.9.6 14 Apr 2017 C1 H1 MIT No Details →
0.9.5 07 Apr 2017 C1 H1 MIT No Details →
0.9.4 16 Jan 2017 C1 H1 MIT No Details →
0.9.3 04 Jan 2017 C1 H1 MIT No Details →
0.9.2 22 Dec 2016 C1 H1 MIT No Details →
0.9.1 22 Nov 2016 C1 H1 MIT No Details →
0.9.0 19 Sep 2016 C1 H1 MIT No Details →
0.8.5 16 Jul 2016 C1 H1 MIT No Details →
0.8.4 04 Jul 2016 C1 H1 MIT No Details →
0.8.3 14 Jun 2016 C1 H1 MIT No Details →
0.8.2 28 May 2016 C1 H1 MIT No Details →
0.8.0 19 Apr 2016 C1 H1 MIT No Details →
0.7.5 15 Dec 2015 C1 H1 MIT No Details →
0.7.5-beta 15 Dec 2015 C1 H1 MIT No Details →
0.7.3 06 Dec 2015 C1 H1 MIT No Details →
0.7.2 28 Oct 2015 C1 H1 MIT No Details →
0.7.1 15 Sep 2015 C1 H1 MIT No Details →
0.7.0 22 Jul 2015 C1 H1 MIT No Details →
0.7.0-beta1 06 Jul 2015 C1 H1 MIT No Details →
0.6.2 11 Jun 2015 C1 H1 MIT No Details →
0.6.1 11 Jun 2015 C1 H1 MIT No Details →
0.6.0 14 May 2015 C1 H1 MIT No Details →
0.5.0-alpha.6 10 Mar 2015 C1 H1 MIT No Details →
0.5.0-alpha.5 30 Jan 2015 C1 H1 MIT No Details →
0.5.0-alpha.4 30 Jan 2015 C1 H1 MIT No Details →
0.5.0-alpha.3 30 Jan 2015 C1 H1 MIT No Details →
0.5.0-alpha.2 30 Jan 2015 C1 H1 MIT No Details →
0.4.11 24 Jan 2015 C1 H1 MIT No Details →
0.4.10 08 Jan 2015 C1 H1 MIT No Details →
0.4.9 28 Dec 2014 C1 H1 MIT No Details →
0.4.8 19 Dec 2014 C1 H1 MIT No Details →
0.4.7 18 Dec 2014 C1 H1 MIT No Details →
0.4.6 25 Sep 2014 C1 H1 MIT No Details →
0.4.5 14 Aug 2014 C1 H1 MIT No Details →
0.4.4 08 Aug 2014 C1 H1 MIT No Details →
0.4.3 24 Dec 2013 C1 H1 MIT No Details →
0.4.2 03 Sep 2013 C1 H1 MIT No Details →
0.4.1 27 Aug 2013 C1 H1 MIT No Details →
0.4.0 26 Aug 2013 C1 H1 MIT No Details →
0.3.16 26 Aug 2013 C1 H1 MIT No Details →
0.3.15 07 Aug 2013 C1 H1 MIT No Details →
0.3.14 01 Aug 2013 C1 H1 MIT No Details →
0.3.13 16 Apr 2013 C1 H1 MIT No Details →
0.3.12 11 Mar 2013 C1 H1 MIT No Details →
0.3.11 11 Mar 2013 C1 H1 MIT No Details →
0.3.10 11 Mar 2013 C1 H1 MIT No Details →
0.3.9 09 Mar 2013 C1 H1 MIT No Details →
0.3.8 05 Mar 2013 C1 H1 MIT No Details →
0.3.7 27 Feb 2013 C1 H1 MIT No Details →
0.3.6 20 Feb 2013 C1 H1 MIT No Details →
0.3.5 19 Feb 2013 C1 H1 MIT No Details →
0.3.4 17 Feb 2013 C1 H1 MIT No Details →
0.3.3 25 Jan 2013 C1 H1 MIT No Details →
0.3.2 25 Jan 2013 C1 H1 MIT No Details →
0.3.1 24 Jan 2013 C1 H1 MIT No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for velocityjs

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Remote Code Execution Vulnerability in Velocity.js (v2.1.6) 9.8 critical 2.1.7 24 Jul 2026
CVE-2026-44966: Velocity.js Prototype Pollution Vulnerability 8.3 high No fix published 09 May 2026

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 velocityjs

Is velocityjs safe to use?

Vulert records 2 vulnerabilities for velocityjs in npm: 1 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 velocityjs's Vulert package health score?

Vulert scores velocityjs 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of velocityjs affected?

Yes. 2.1.7, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of velocityjs should I use?

2.1.7 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 velocityjs have?

2 vulnerabilities are recorded for velocityjs in the npm ecosystem: 1 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 velocityjs vulnerabilities disclosed?

2 vulnerabilities were recorded for velocityjs in the last 12 months, and the oldest entry in this database dates to 09 May 2026. 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 velocityjs 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 velocityjs for upcoming vulnerabilities?

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