Nodejs 22.x Vulnerability

Hello,

I have been using ondemand version, nodejs version, ondemand-nodejs below
ondemand-4.2.3-1.el9.x86_64
nodejs-22.23.2-2.module
ondemand-nodejs-4.2.0-1.el9.x86_64

There is a security vulnerability in Node.js version 22.x related to these versions.

which version have been using by Ondemand_4.2.3.1 packet and is it suitable with nodejs 22.23.4 or newer version ?

How can I resolve this without updating the Ondemand_4.2.3.1 package?

Kind Regards

Details

dns.resolve truncates names containing NUL char (CVE-2026-105482) - (high)
This vulnerability affects Node.js 26.x, 24.x, and 22.x.

TLS certificate hostname bypass when the IP is written fullwidth digits (CVE-2026-105483) - (high)
This vulnerability affects Node.js 26.x and 24.x.

TLS certificate hostname bypass when the host loosely resolves to an IP address (CVE-2026-106069) - (high)
This vulnerability affects Node.js 26.x, 24.x, and 22.x.

Node.js Brotli decoder out-of-bounds write permits remote code execution (CVE-2026-111497) - (high)
A flaw in Node.js can cause Node.js Brotli decoder out-of-bounds write permits remote code execution.

This vulnerability affects Node.js 26.x, 24.x, and 22.x.

Keep-alive socket process a response that was written before the request was sent (CVE-2026-105481) - (medium)
This vulnerability affects Node.js 26.x, 24.x, and 22.x.

Improper certificate validation for non-canonical IPv4 hostnames allows DNS SANs to authenticate IP endpoints (CVE-2026-106072) - (medium)
This vulnerability affects Node.js 26.x, 24.x, and 22.x.

crypto.randomUUID() and randomInt() entropy caches are saved into user-land startup snapshots and SEAs, so every process repeats the same values (CVE-2026-106074) - (medium)
This vulnerability affects Node.js 26.x, 24.x, and 22.x.

Permission Model bypass with fs.realpathSync (CVE-2026-106073) - (low)
This vulnerability affects Node.js 26.x, 24.x, and 22.x.

You should be able to just update the nodejs-22 module from dnf. Does that give errors if you do?

Thank you so much for the advice, but for now there is no patch and updated packet

I am thinking RHEL/Rocky/Alma isn’t going to patch nodejs-22 … the patched version is 22.23.4 and they still haven’t put 22.23.3 in the repos.

will nodejs-24 work? is there a plan/timeline to bump up the dependency in OOD to 24 or maybe even nodejs-26?

No the package has the version requirement, but even if you were to get around that, the shell app is compiled to 22.

Not at this time. We did this once when some node version went EOL during our patch cycles. But that case was it wasn’t going to get any updates ever.

A quick search shows RHEL has node-js 22 EOL at April of next year which suggests they should patch it.

Looking at the RHEL documentation 22 is listed as Affected and FAQ says Affected means they “may patch it”

Looking through RHEL’s bugzilla I see a lot of nodejs22 items in the IN_QA status, so I’m guessing the updates are working their way through the system.

thank you so much for the question @jleister and for the answer @jeff.ohrstrom
we have disabled our Open Ondemand Server right now and we don’t know yet which direction related this vulnerability should we go. Because there is no patch nodejs-22 and Open OnDemand does not work nodejs-24.

So what would be your suggestion to use Open OnDemand @jeff.ohrstrom ?
should we use nodejs-18 or older version which we don’t know that are also affected or not?

Which Open OnDemand version can we use ?

Best Regards

You can run OnDemand, just disable the shell application as it’s the one that uses nodejs.

Using node 18 would have the same issues as node 24.

That said - I’m not sure if any of these are actually exploitable in the shell app in OnDemand. Most rely on user input that has to call the specific functionality like dns lookups (which we don’t do). Or the fact that we use a per user nginx so all requests are yours’ anyhow - you can’t see some else’s request or data.

OnDemand v3.1 supports nodejs18 right? I mean that can be used

there is no any OnDemand version supports nodejs-24

I guess so, but OnDemand has it’s own vulnerabilities that have been patched past 3.1. I.e., 3.1 is vulnerable to some of them.

But as I say, you can disable the shell application to avoid nodejs. That’s the only component that uses nodejs, so you’d still get to keep a lot of OnDemand functionality while users use Putty or similar programs for sshing.

RHEL has released nodejs-22.23.4-2 for EL9

See https://access.redhat.com/errata/RHSA-2026:96234 for package names. I just update my dev system (Rocky 9) to nodejs-22.23.4-2.module+el9.8.0+40414+05b896b7.x86_64

The changelog shows

  • Mon Nov 02 2026 Tomas Juhasz tjuhasz@redhat.com - 1:22.23.4-1

  • Rebase to version 22.23.4
    Fixes: CVE-2026-102278 CVE-2026-102276 CVE-2026-109869 CVE-2026-109383
    CVE-2026-109829 CVE-2026-105482 CVE-2026-106069 CVE-2026-87018
    Resolves: RHEL-281706 RHEL-282244 RHEL-284791 RHEL-284810 RHEL-284822
    RHEL-284880 RHEL-291379 RHEL-291405 RHEL-289765

which seems to address the issues in this thread.

Thank you very much @ric . It seems to be solving the problem for now and I think we can continue using version 4.2.3.1.