Skip to main content
Lead Generation Websites, Google Maps Ranking, WhatsApp Funnels, Ecommerce, SEO, Web DesignSpeed Optimization · Conversion Optimization · Monthly Lead Systems · AI AutomationLead Generation Websites, Google Maps Ranking, WhatsApp Funnels, Ecommerce, SEO, Web Design
November 19, 202611.19.26

Node.js Security Release Checklist for Self-Hosted Next.js Sites

A reusable checklist for self-hosted Next.js sites: Node.js version, support, restart, staging and rollback, with the 11 Nov 2026 release as the example.

Node.js Security Release Checklist for Self-Hosted Next.js Sites

A self-hosted Next.js site needs four checks whenever the Node.js project ships a security release. Know which Node.js version each app really runs. Know whether you or your host installs the patch. Restart the process so it uses the patched binary. Test it, with a rollback ready. As of 6 November 2026, Node.js has pre-announced a security release for its 22.x, 24.x and 26.x lines on or shortly after 11 November, with a highest severity of HIGH. This post turns that notice into a checklist you can reuse for any Node.js security release, with the November notice as a dated worked example.

If you aren't sure where your Node.js version comes from, start with how the app was deployed. We cover the two common setups in our guides to deploying Next.js on cPanel with Phusion Passenger and running Node.js on Linux with Nginx and PM2. This page assumes the app already runs and covers what has to happen in the week a patch lands.

What Node.js has announced for 11 November 2026

The Node.js project's pre-announcement says new 26.x, 24.x and 22.x versions will ship "on or shortly after" Wednesday 11 November 2026. It says the highest severity issue fixed is HIGH in each of those lines. The @nodejs account posted the same pre-alert on 4 November, and the blog page was last updated on 3 November.

No CVE numbers, affected components or fixed version numbers were public when I last read the page on 6 November, so I won't guess at them. Two sentences on that page matter whatever the CVEs turn out to be. The first: "End-of-Life versions are always affected when a security release occurs." The second is a pointer to the release schedule for choosing a version that is still supported.

I wrote this before the release shipped. Before you act on any date here, check the Node.js blog's vulnerability section and the Node.js release status page for what has actually been published. The previous release, on 21 October 2026, shows why your line matters: not every fix applied to every line, as the figures after Step 2 show.

Step 1: Find the Node.js version your self-hosted Next.js app really runs

A self-hosted Next.js app runs on whichever Node.js binary started its process, and that isn't always the one you get when you type node -v in a terminal. One server can hold a system package, an nvm install, a build a host installed for cPanel and the version baked into a Docker image. Check the running process, not your shell.

How you run itWhere the Node.js version is decidedHow to see what is actually running
PM2 on a VPSThe Node.js installed on the server (system package, NodeSource or nvm)Find the process ID with pm2 list, then check its executable path
systemd serviceThe path in the unit's ExecStart lineRead the main process ID from systemctl show, then check its executable path
DockerThe base image tag in your DockerfileRun node -v inside the running container, not on the host
cPanel with PassengerThe Node.js version set for the app, from the packages your host installedThe app's settings screen, then the version logged by the app itself

The most reliable check is to log process.version from inside the app and read it from your logs or a protected health route. Vercel's documentation recommends the same method for functions, and the Node.js docs describe process.version. On Linux you can also read the executable path of a running process, as described on the proc/pid/exe manual page.

List every app, not just the main site. A forgotten staging copy on the same server is the usual surprise.

Step 2: Confirm your Node.js line is still supported

A supported Node.js line is one the project still patches, and on 6 November 2026 that means 22.x, 24.x and 26.x. The project's own guidance is that "production applications should only use Active LTS or Maintenance LTS releases", and it describes odd-numbered releases such as 25 as short-lived. These are the dates from its release schedule:

  • Node.js 22 ("Jod"): Maintenance LTS since 21 October 2025, end of life 30 April 2027.
  • Node.js 24 ("Krypton"): Maintenance LTS from 20 October 2026, end of life 30 April 2028.
  • Node.js 26 ("Lithium"): LTS from 28 October 2026, end of life 30 April 2029.
  • Node.js 20: end of life since 30 April 2026.

There's a trap in the Next.js docs. Their installation page lists Node.js 20.9 as the minimum version, and 20.x is already end of life. "Next.js starts" and "Node.js is patched" are separate questions. If you run 20.x or older, a move to a supported line is the first job, ahead of any November patch.

Key figures for Node.js patch planning

  • 30 April 2027: the scheduled end of life for Node.js 22, the oldest line still patched (24 ends 30 April 2028, 26 ends 30 April 2029, and 20 ended on 30 April 2026), read on 6 November 2026. Source: Node.js release schedule data.
  • 10 CVEs, 4 rated high: in the Node.js security release of 21 October 2026. All ten affected 26.x, eight affected 24.x and seven affected 22.x (my count from the advisory text). Source: Node.js October 2026 security releases.
  • 7 advisories, 1 high and 6 medium: in the Next.js security release of 3 November 2026, fixed in 16.4.5 and 15.5.29. Two are described as affecting self-hosted applications. Source: Next.js November 2026 Security Release.

Step 3: Decide whether your host or you patch Node.js

On a VPS you patch Node.js yourself. On cPanel hosting the provider normally decides which Node.js builds exist, and your app depends on that decision.

The cPanel documentation, as I read it on 6 November 2026, says the provider must install one of the ea-nodejs packages for Application Manager, and it lists versions 16, 18, 20 and 22. It also says installing one Node.js package uninstalls any other, so existing applications must be updated to the new version. Three of those four lines are end of life on the schedule above.

That describes a documentation page, not your host. Send your host these questions and keep the answers:

  • Which exact Node.js version is installed for my app today?
  • Will you install the patched 22.x, 24.x or 26.x build after 11 November, and by when?
  • Can I choose 24.x or 26.x, and who restarts my app after the change?
  • If my line is end of life on your servers, what is the upgrade path?

A reply of "we handle it" that doesn't name a version hasn't answered anything.

Not sure which Node.js version your site runs, or whether your host will patch it? We check your servers and apps and tell you what needs to change.

Request a Node.js and Next.js patch check

Step 4: Restart or redeploy so the patched Node.js is used

A running Node.js process keeps the binary it started with, so installing a patched version does nothing for an app until that process restarts. Passenger's documentation makes the same point for application changes: it keeps application processes around between requests, so changes don't take effect until the application restarts, and it recommends passenger-config restart-app.

  1. PM2 or a plain process: restart after the package or nvm change, then read the version from the running process.
  2. systemd: restart the unit and confirm ExecStart points at the binary you patched.
  3. Docker: pulling an image is not enough. Rebuild with docker build --pull so the base image is refreshed (the Docker docs describe the flag), then redeploy the container.
  4. cPanel and Passenger: restart the app from cPanel or with passenger-config restart-app, then check the logged version.

Moving between major lines, say 22 to 24, is a bigger step than a patch. Reinstall dependencies and run next build on the new version, because packages with native parts are built for a specific Node.js version. A patch inside the same line normally doesn't need that, but run the staging test either way.

Step 5: Test on staging, watch health checks, keep a rollback

A staging copy on the same Node.js version and the same reverse proxy catches most surprises before visitors do. The Next.js self-hosting guide recommends putting a reverse proxy such as nginx in front of the Next.js server instead of exposing it directly, so test through the proxy. A short smoke test covers it:

  • A statically generated page and a dynamic page.
  • A page that uses revalidation or incremental static regeneration, after a deploy.
  • An image served through next/image, since Image Optimization runs on your server.
  • A form submission or Server Action.
  • A streaming page through the proxy. The Next.js docs say nginx must have buffering disabled for streaming to work.

After the production restart, hit a health URL that returns process.version and the Next.js version, and read the startup logs for errors. Write the rollback down before you start: the previous Docker image tag, the previous Node.js install path, and the last good build, plus the exact command to switch back. If you roll back, treat it as temporary and note the exposure, because the older version still lacks the fix.

Runtime patching doesn't replace application-level hardening such as rate limiting and security headers, which our Node.js security basics guide covers.

Self-hosted Next.js versus Vercel: which advisories need your attention

Node.js patching is half the work, because Next.js ships its own security releases. On Vercel, the platform documents that only major Node.js versions are selectable and that it "automatically rolls out minor and patch updates when needed, such as to fix a security issue". Self-hosted, that job is yours. Next.js advisories are less uniform, so read each one:

AdvisoryApplies when, per Next.jsRelease
Cache poisoning of SSG and ISR pages (CVE-2026-94543)Self-hosted apps using the Pages Router with SSG or ISR; applications deployed on Vercel are not affected30 Sep 2026 (16.3.8, 15.5.27)
Shared shell cache poisoningSelf-hosted apps running next start with Cache Components enabled and Partial Prefetching off or unset, with a specific route shape3 Nov 2026 (16.4.5, 15.5.29)
Stale compressed response framingSelf-hosted apps that return a fetched response unchanged, behind an HTTP/1.1 reverse proxy that queues pipelined requests on a shared backend connection; not every proxy setup3 Nov 2026 (16.4.5, 15.5.29)

The last row shows why you can't skip the reading. A reverse proxy is a control Next.js recommends, and in that advisory the proxy's behaviour is part of the condition. If you can't tell from your configuration whether an advisory applies, patch anyway. Node.js and Next.js are updated separately, so do both and test once. For the wider picture of owning these updates, see our overview of Next.js in 2026, or our Next.js development service if you'd rather we run it.

Step 6: Keep a dated record

A record of each patch makes the next release much quicker to handle. After every Node.js or Next.js update, note:

  • The date, time and who did it.
  • Each app's Node.js and Next.js versions before and after, read from the running process.
  • The release notice you acted on, with its link.
  • The staging test result and whether the rollback was ready.

Watch: Self-Hosting Next.js

A video from the channel leerob that the official Next.js self-hosting guide links to. I haven't checked it against the 2026 advisories, so use it for background on infrastructure choices, not for patch advice.

Watch on YouTube: Self-Hosting Next.js

Still deciding whether to keep running servers yourself? Compare what each hosting route asks of you before the next security release.

Compare hosting options for your Next.js site

Reference reading

Frequently Asked Questions

How do I check which Node.js version my Next.js site is running?

Log process.version from inside the running app and read it from your logs or a protected health route. The version in your SSH shell can differ from the one serving traffic, so don't rely on node -v alone. Check staging as well as production.

Is Node.js 20 still safe for a Next.js site?

Node.js 20 reached end of life on 30 April 2026 and no longer receives security fixes. The Node.js project says end-of-life versions are always affected when a security release occurs. Next.js still lists 20.9 as its minimum version, so the framework starting is not proof the runtime is patched. Move to 22.x, 24.x or 26.x.

Do I need to patch Node.js if my Next.js site is on Vercel?

Vercel documents that it rolls out minor and patch Node.js updates itself when needed, such as to fix a security issue, so you don't install them. You still choose the major version and you still update Next.js. Whether a Next.js advisory applies to Vercel is stated per advisory, not as a blanket rule.

Does updating Node.js also fix the Next.js advisories?

No, because the two are patched separately. The 3 November 2026 Next.js release is fixed by upgrading the next package to 16.4.5 or 15.5.29, whatever your Node.js version. Update both and run one staging test.

When should I apply the Node.js update after 11 November?

Apply it once the fixed versions are published, your staging test passes and your rollback is ready. The pre-alert says "on or shortly after" 11 November, so check the Node.js release status for the real date. For a HIGH severity release I wouldn't wait for the next monthly maintenance slot.

Comments

Leave a Comment

Loading comments...