Node.js comes bundled with Qlik Sense Enterprise on Windows. Its version depends on the Qlik Sense released currently installed.
How do I know which version of node.js is used by Qlik Sense?
You can verify the version of any of the third-party integrations Qlik Sense makes use of by:
Using the Qlik Sense API and calling About Service API: thirdParty: Get, which returns details including information about copyright, version, licensing, and legal notices.
Accessing the below URL in a browser, where qlikserver.domain.local is replaced with your Qlik Sense server hostname:
How do I upgrade my version of node.js is used by Qlik Sense?
You may want to upgrade node.js, specifically in response to a security vulnerability. To do so, upgrade Qlik Sense Enterprise on Windows. When upgrading Qlik Sense, the currently installed node.exe will be replaced with the version Qlik Sense comes bundled with at this release.
Can I install or upgrade a separately installed instance of node.js?
Installing Qlik Sense installs node.exe side-by-side in the following location: C:\Program Files\Qlik\Sense\ServiceDispatcher\Node.
If you install node.js manually it will typically be installed in C:\Program Files\nodejs and the Windows environment variable will point to this location by default (i.e. running node -v to get the version will result in providing the version of node found in C:\Program Files\nodejs).
As Qlik Sense will not register any Windows environment variable for node.js, it will not tamper with any settings affecting already installed node.js instances. Therefore it is safe to upgrade your separate instance of Node.js.
Sorry for reaching out under this post, but this is the only Node JS related article/forum I could find. Here is the post that I've created Qlik Sense Node JS Vulnerability. Would really appreciate if you could help me with this. But here is a quick summary "whether Qlik has addressed vulnerabilities related to Node JS 1.7.8 (used in QlikSense May 2024 Patch 21) in a recent version or upcoming patch, specifically regarding issues with Angular JS, Koa, body-parser, and other dependencies which seem to be a part of NodeJs version being used."