Red Hat Security Advisory: nodejs22 security, bug fix, and enhancement update
Affects Red Hat nodejs22 security,Source GCVE Database
Mentioned vulnerabilities
Not known to be exploited.
Data as of 17 Nov 2026, 20:25 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 6 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Product Security Red Hat | Affected
| Fixed in– |
AI-suggested
Red Hat has released an updated nodejs22 package rebased to the latest Node.js 22 release that addresses all listed vulnerabilities. Users of Red Hat Enterprise Linux 10 should apply this update promptly to remediate these security issues. Detailed update instructions are available in the Red Hat advisory at https://access.redhat.com/articles/11258. No additional mitigations are specified beyond applying the official update. There are no indications that these vulnerabilities are currently exploited in the wild.
Description
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): * ip-address: ip-address: Cross-site scripting via improper HTML escaping of untrusted input (CVE-2026-42338) * undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (CVE-2026-12151) * undici: Undici: Information disclosure due to improper cache-control header parsing (CVE-2026-9678) * undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery. (CVE-2026-6733) * undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (CVE-2026-11525) * 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: Authentication bypass due to TLS hostname handling and unicode dot separator mismatch (CVE-2026-48618) Bug Fix(es) and Enhancement(s): * nodejs22: Rebase to the latest Node.js 22 release [rhel-10.2.z] (JIRA:RHEL-186623) 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.
References
- access.redhat.com/errata/RHSA-2026:35842 (opens in a new tab)
- access.redhat.com/security/updates/classification/ (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2476810 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2489980 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2490000 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2490006 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2490008 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2493325 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2493326 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2493329 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2493331 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2493332 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2493333 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2493335 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2493337 (opens in a new tab)
- issues.redhat.com/browse/RHEL-186623 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_35842.json (opens in a new tab)
- suse.com/support/security/rating/ (opens in a new tab)
- ftp.suse.com/pub/projects/security/csaf/rhsa-2026_35842.json (opens in a new tab)
- lists.suse.com/pipermail/suse-liberty-linux-updates/2026-July/006884.html (opens in a new tab)
- suse.com/security/cve/CVE-2026-11525/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-12151/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-42338/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-48615/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-48617/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-48618/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-48619/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-48928/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-48930/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-48931/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-48933/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-48934/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-48935/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-48937/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-6733/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-9678/ (opens in a new tab)