RLSA-2026:98619: Important: nodejs26 security, bug fix, and enhancement update
Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.
Security Fix(es):
nodejs: Node.js: Permission Model bypass via process.report.writeReport() path misvalidation (CVE-2026-48617)
nodejs: Node.js HTTP Agent: Information disclosure due to premature response acceptance (CVE-2026-48931)
nodejs: Node.js: Denial of Service via unlimited HTTP/2 ORIGIN frames (CVE-2026-48619)
nodejs: Node.js: Silent authority rebinding due to embedded-nul hostnames in TLS handling (CVE-2026-48930)
nodejs: Node.js: Unauthorized file metadata modification (CVE-2026-48935)
nodejs: Node.js WebCrypto: Denial of Service via large input to subtle.encrypt() (CVE-2026-48933)
nodejs: Node.js: Certification validation bypass in TLS host verification (CVE-2026-48934)
Node.js: Node.js: Trust-policy bypass due to hostname matching inconsistency (CVE-2026-48928)
nodejs: Node.js: Information disclosure of proxy credentials via proxy tunnel error handling (CVE-2026-48615)
nodejs: Node.js: Local server can be started without network permission via Permission API flaw (CVE-2026-48936)
nodejs: Node.js: Authentication bypass due to TLS hostname handling and unicode dot separator mismatch (CVE-2026-48618)
undici: undici: Information disclosure and Denial of Service via malformed Cache-Control directives (CVE-2026-13697)
nodejs: Node.js: Unauthorized filesystem access due to Permission Model enforcement flaw (CVE-2026-58043)
nodejs: HTTPS Agent TLS session reuse skips hostname verification (CVE-2026-58040)
nodejs: Node.js: Permission Model flaw allows trace logs to bypass filesystem write restrictions (CVE-2026-56847)
nodejs: Node.js: mTLS client identities can be reused due to HTTPS Agent connection flaw (CVE-2026-56850)
nodejs: Information disclosure due to improper permission enforcement (CVE-2026-58039)
nodejs: Node.js: Request smuggling via HTTP client header truncation (CVE-2026-58044)
nodejs: Node.js: Denial of Service via DNS responses with excessive A records (CVE-2026-58042)
nodejs: Node.js: Denial of Service vulnerability (CVE-2026-58045)
nodejs: Node.js node:sqlite: Unintended data modification due to stale statement iterator (CVE-2026-58041)
nodejs: Node.js: Heap-use-after-free in HTTP/2 handling can lead to denial of service (CVE-2026-56848)
brace-expansion: brace-expansion: Denial of Service via uncontrolled recursion in nested brace patterns (CVE-2026-102278)
brace-expansion: brace-expansion: Denial of Service via stack exhaustion from crafted brace patterns (CVE-2026-102276)
undici: undici: Denial of Service via unhandled stream error on excessive content encodings (CVE-2026-109869)
undici: undici: Denial of Service via TLS renegotiation with mismatched certificate (CVE-2026-87018)
undici: undici: Certificate validation bypass via dropped TLS options in Agent (CVE-2026-109383)
undici: undici: Cache poisoning and information disclosure via improper cross-origin redirect caching (CVE-2026-109829)
nodejs: nodejs: TLS certificate hostname bypass via fullwidth-digit IP hostnames (CVE-2026-105483)
nodejs: nodejs: TLS certificate hostname bypass via non-canonical IP hostnames (CVE-2026-106069)
nodejs: nodejs: dns.resolve truncates hostnames containing a NUL character (CVE-2026-105482)
Bug Fix(es) and Enhancement(s):
nodejs26: Rebase to the latest Node.js 26 release [rhel-10.3.z] (JIRA:Rocky Linux-295502)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
rocky-linux/nodejs26-libs-debuginfoto a version that resolves this vulnerability.Fixed in 1:26.12.1-3.el10_3 - Upgrade
Upgrade
rocky-linux/nodejs26to a version that resolves this vulnerability.Fixed in 1:26.12.1-3.el10_3 - Upgrade
Upgrade
rocky-linux/nodejs26-full-i18nto a version that resolves this vulnerability.Fixed in 1:26.12.1-3.el10_3 - Upgrade
Upgrade
rocky-linux/nodejs26-debugsourceto a version that resolves this vulnerability.Fixed in 1:26.12.1-3.el10_3 - Upgrade
Upgrade
rocky-linux/nodejs26-develto a version that resolves this vulnerability.Fixed in 1:26.12.1-3.el10_3 - Upgrade
Upgrade
rocky-linux/nodejs26-debuginfoto a version that resolves this vulnerability.Fixed in 1:26.12.1-3.el10_3 - Upgrade
Upgrade
rocky-linux/nodejs26-libsto a version that resolves this vulnerability.Fixed in 1:26.12.1-3.el10_3 - Upgrade
Upgrade
rocky-linux/nodejs26-docsto a version that resolves this vulnerability.Fixed in 1:26.12.1-3.el10_3 - Upgrade
Upgrade
rocky-linux/nodejs26-npmto a version that resolves this vulnerability.Fixed in 1:11.20.0-1.26.12.1.3.el10_3
Event History
Child vulnerabilities
Contains the following vulnerabilities.
- CVE-2026-102276
- CVE-2026-102278
- CVE-2026-105482
- CVE-2026-105483
- CVE-2026-106069
- CVE-2026-109383
- CVE-2026-109829
- CVE-2026-109869
- CVE-2026-13697
- CVE-2026-48615
- CVE-2026-48617
- CVE-2026-48618
- CVE-2026-48619
- CVE-2026-48928
- CVE-2026-48930
- CVE-2026-48931
- CVE-2026-48933
- CVE-2026-48934
- CVE-2026-48935
- CVE-2026-48936
- CVE-2026-56847
- CVE-2026-56848
- CVE-2026-56850
- CVE-2026-58039
- CVE-2026-58040
- CVE-2026-58041
- CVE-2026-58042
- CVE-2026-58043
- CVE-2026-58044
- CVE-2026-58045
- CVE-2026-87018
Frequently Asked Questions
Which installed packages should be reviewed for exposure?
Review systems with rocky-linux/nodejs26, nodejs26-libs, nodejs26-devel, nodejs26-docs, nodejs26-full-i18n, or the associated debuginfo and debugsource packages installed. The advisory identifies these packages as affected by the update.
What does the supplied severity vector indicate about exploitation conditions?
The supplied vector indicates network reachability, low attack complexity, low required privileges, and no user interaction. It also indicates a changed scope and high confidentiality impact.