Following the recently disclosed vulnerabilities on eMudhra issued certificates, we have reviewed Nintex RPA and Nintex RPA does not ship or require eMudhra certificates.
However, two third-party components bundled with RPA, OpenJDK and Node.js, have since been updated by their vendors to address the issue. Below are step-by-step guides for upgrading them.
We recommend applying these upgrades as a proactive security measure. Each guide includes validation and rollback steps.
Check your SSL certificate
Besides these upgrades, if you supplied your own SSL certificate during RPA installation, check whether it was issued by an affected eMudhra Certificate Authority. If it was, run the Repair function of the RPA server installer and provide a new certificate.
» Refer here for the guide to upgrade OpenJDK
Upgrade Node.js
Version Reference
Use the Node.js version that corresponds to your RPA.
| RPA Release | Node.js Version | Download |
| v26.6 | v24.22.2 | |
| v25.11 | v22.23.4 |
Path Conventions
The steps in this guide use the following placeholders. Replace them with the actual paths on your server.
| Placeholder | Meaning | Example |
| {nintex dir} | RPA installation folder that contains StopAll.bat | C:\Program Files\Nintex\RPA |
| {Program Files} | Program Files folder | C:\Program Files |
| {node dir} | Folder created by extracting the Node.js archive | C:\Program Files\nodejs\node-v24.22.2-win-x64 |
Prerequisites
An account that can run programs as Administrator on the server. Elevation is required to run StopAll.bat and to change the system Path variable.
Apply the Upgrade
-
Stop all RPA services by running {nintex dir}\StopAll.bat as Administrator.
-
Extract the ZIP archive to {Program Files}\nodejs. The archive creates its own versioned folder, e.g. C:\Program Files\nodejs\node-v24.22.2-win-x64
-
Record and remove the existing Node.js path. Open Environment Variables > System variables > Path. Note the existing Node.js entry (for example, C:\Program Files\nodejs\node-<previous version>-win-x64) so that it can be restored if a rollback is needed, and then delete that entry.
-
Add the new Node.js path - in the same Path variable, add the {node dir} folder from step
-
Restart the server and confirm that all RPA services are running.
-
To validate the Node.js runtime, open a new Command Prompt and run the following commands:
where node
node -v
npm -vnode -v should report the new version, and where node should list only the new path first.
-
To validate the applications, confirm that Studio, Robot and Console work as expected.
Reverting the Upgrade
If validation fails, restore the previous Node.js runtime as follows.
-
Stop all RPA services by running {nintex dir}\StopAll.bat as Administrator.
-
In the system Path variable, remove the new {node dir} entry that you added in step 4 of the upgrade, and then add back the original Node.js entry that you recorded in step 3.
-
Restart the server and repeat steps 6 and 7 of the upgrade to confirm that the previous runtime is working.
Notes
-
Keep the previous Node.js folder on disk until validation has passed, so that a rollback requires only a change to the Path variable.