porro

End of life  /  Node.js  /  17

End of life

Node.js 17 is past end of life.

Security fixes stopped on 1 Jun 2022, 1611 days ago. New vulnerabilities in 17 won’t be fixed.

Released
19 Oct 2021
Active support
ended 1 Apr 2022
Security fixes
ended 1 Jun 2022
Latest
17.9.1

Upgrade to Node.js 26: security fixes until 30 Apr 2029.

What to upgrade to

Go to 26.

26 is the newest supported long-term Node.js cycle, with security fixes until 30 Apr 2029.

Before you upgrade

Even-numbered releases become LTS; odd ones never do. Move build servers and CI to the same version, then reinstall node_modules. Read the Node.js 26 upgrade guide

How to check your version

Which Node.js is this site on?

On the server

$ node -v
v22.11.0
# build servers and CI can run a different version

In the project

$ cat .nvmrc package.json | grep -A2 engines
# engines and .nvmrc say what you expect, not what runs

On Forge

Server → Node
Node version: 22
# set per server, used by deploy scripts

Know before support ends.

Porro reads the PHP, framework and database version from every site and tells you 90 days before support runs out.

Start your free trial →

Dates from endoflife.date/nodejs, checked daily · data as of 29 Oct 2026.