Red Hat Updates Node.js 22 Modules on RHEL 9
Tech GuruQuick Answer
Check Node.js 22 on RHEL 9 nodejs:22 module. Apply RHSA-2026:96234 from the matching entitled repository. Restart Node.js processes, confirm the active module/runtime and test TLS validation, network calls and application health.
Confirm Scope And Apply The Supported Remediation
What to do now: Record the enabled Node.js module, complete RPM versions, outbound TLS clients and affected bundled dependencies. RHEL 9 nodejs:22 module: installations of the Node.js 22 packages requiring RHSA-2026:96234. Match the full installed RPM, architecture and repository to the vendor product tree; a universal upstream version range is not stated. Apply RHSA-2026:96234 through the entitled Red Hat repositories. The fixed source builds are nodejs-1:22.23.4-2.module+el9.8.0+25286+62e50b69::nodejs:22; nodejs-nodemon-0:3.1.14-3.module+el9.8.0+25286+62e50b69::nodejs:22; nodejs-packaging-0:2021.06-6.module+el9.8.0+24709+804d6b5b::nodejs:22. Install the matching binary packages for the supported stream and architecture. Restart Node.js processes, confirm the active module/runtime and test TLS validation, network calls and application health.
Last verified: 2026-11-09 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | RHEL 9 nodejs:22 module; Node.js 22 |
|---|---|
| Advisory | RHSA-2026:96234 |
| CVEs | CVE-2026-102276, CVE-2026-102278, CVE-2026-105482, CVE-2026-106069, CVE-2026-109383, CVE-2026-109869, CVE-2026-87018 |
| Authoritative release date | November 9, 2026 at 12:43:25 UTC, from Red Hat CSAF initial_release_date. |
| Authority revision date | Red Hat records the substantive last-updated version at 2026-11-09T12:43:25+00:00. The CSAF generation timestamp is 2026-11-09T16:42:56+00:00; generation alone is not a material advisory revision. |
| Affected versions | RHEL 9 nodejs:22 module: installations of the Node.js 22 packages requiring RHSA-2026:96234. Match the full installed RPM, architecture and repository to the vendor product tree; a universal upstream version range is not stated. |
| Fixed version | nodejs-1:22.23.4-2.module+el9.8.0+25286+62e50b69::nodejs:22; nodejs-nodemon-0:3.1.14-3.module+el9.8.0+25286+62e50b69::nodejs:22; nodejs-packaging-0:2021.06-6.module+el9.8.0+24709+804d6b5b::nodejs:22 |
| CVSS base score | 7.5 (highest authority-stated CVSS 3.1 base score) |
| CVSS severity | High (CVSS); Important (Red Hat impact) |
| Exploitation status | Red Hat does not state exploitation in this advisory.; no exploitation claim is inferred. |
Authority CVSS by Vulnerability
| CVE-2026-87018 | CVSS 3.1: 7.5 (High) |
|---|---|
| CVE-2026-102276 | CVSS 3.1: 7.5 (High) |
| CVE-2026-102278 | CVSS 3.1: 6.5 (Medium) |
| CVE-2026-105482 | CVSS 3.1: 7.4 (High) |
| CVE-2026-106069 | CVSS 3.1: 7.4 (High) |
| CVE-2026-109383 | CVSS 3.1: 7.4 (High) |
| CVE-2026-109869 | CVSS 3.1: 7.5 (High) |
What Changed
Red Hat released RHSA-2026:96234 for RHEL 9 nodejs:22 module, addressing DNS hostname truncation, TLS hostname and certificate validation bypasses, and dependency denial of service. The update provides the distribution packages listed below; keep the Red Hat release and support channel matched during remediation.
What To Validate Now
- Inventory. Record the enabled Node.js module, complete RPM versions, outbound TLS clients and affected bundled dependencies.
- Establish applicability. RHEL 9 nodejs:22 module: installations of the Node.js 22 packages requiring RHSA-2026:96234. Match the full installed RPM, architecture and repository to the vendor product tree; a universal upstream version range is not stated.
- Remediate. Apply RHSA-2026:96234 through the entitled Red Hat repositories. The fixed source builds are nodejs-1:22.23.4-2.module+el9.8.0+25286+62e50b69::nodejs:22; nodejs-nodemon-0:3.1.14-3.module+el9.8.0+25286+62e50b69::nodejs:22; nodejs-packaging-0:2021.06-6.module+el9.8.0+24709+804d6b5b::nodejs:22. Install the matching binary packages for the supported stream and architecture.
- Validate. Restart Node.js processes, confirm the active module/runtime and test TLS validation, network calls and application health.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Preserve the selected module stream and repository. Independently installed npm packages and bundled applications require separate review; avoid module switching as an untested remediation shortcut.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
Advisory facts are attributed to Red Hat Inc. The linked CSAF content is licensed under CC BY 4.0; TechGeeks operational guidance is summarized for this notice.
