CVE-2026-48618: CWE-176 Improper Handling of Unicode Encoding in nodejs node
A flaw in Node.js TLS hostname handling can cause Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismat. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
AI Analysis
Technical Summary
CVE-2026-48618 is a vulnerability in Node.js where improper handling of Unicode encoding in TLS hostname verification causes a mismatch between resolver and verifier hostname normalization. This leads to a TLS wildcard-depth authentication bypass, undermining the security boundary and potentially exposing confidential information. The vulnerability affects Node.js versions 22, 24, and 26, specifically including versions 22.22.3, 24.16.0, and 26.3.0. The issue is classified under CWE-176 (Improper Handling of Unicode Encoding) and CWE-289 (Authentication Bypass). Red Hat has published multiple advisories and errata providing security updates that fix this vulnerability in their Node.js builds. The CVSS score of 7.7 reflects a high severity with network attack vector, low attack complexity, requiring low privileges, no user interaction, and a confidentiality impact with no integrity or availability impact.
Potential Impact
The vulnerability allows an attacker to bypass TLS hostname verification due to Unicode dot separator normalization mismatches, potentially leading to unauthorized access beyond intended security boundaries. This can result in confidentiality breaches of sensitive data transmitted over TLS connections. There is no reported impact on integrity or availability. The flaw affects all supported Node.js release lines (22, 24, 26) and specific versions identified by Red Hat advisories.
Mitigation Recommendations
Red Hat has released security updates addressing this vulnerability in their Node.js packages. Users should apply the relevant updates from Red Hat advisories (e.g., RHSA-2026:39246) to remediate the issue. Since this is not a cloud service, remediation requires updating the affected Node.js versions. Patch status is confirmed via Red Hat advisories. No vendor advisory indicates that no action is required; therefore, applying the official patches is recommended.
CVE-2026-48618: CWE-176 Improper Handling of Unicode Encoding in nodejs node
Description
A flaw in Node.js TLS hostname handling can cause Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismat. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
CVSS v3.0
Score 7.7high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-48618 is a vulnerability in Node.js where improper handling of Unicode encoding in TLS hostname verification causes a mismatch between resolver and verifier hostname normalization. This leads to a TLS wildcard-depth authentication bypass, undermining the security boundary and potentially exposing confidential information. The vulnerability affects Node.js versions 22, 24, and 26, specifically including versions 22.22.3, 24.16.0, and 26.3.0. The issue is classified under CWE-176 (Improper Handling of Unicode Encoding) and CWE-289 (Authentication Bypass). Red Hat has published multiple advisories and errata providing security updates that fix this vulnerability in their Node.js builds. The CVSS score of 7.7 reflects a high severity with network attack vector, low attack complexity, requiring low privileges, no user interaction, and a confidentiality impact with no integrity or availability impact.
Potential Impact
The vulnerability allows an attacker to bypass TLS hostname verification due to Unicode dot separator normalization mismatches, potentially leading to unauthorized access beyond intended security boundaries. This can result in confidentiality breaches of sensitive data transmitted over TLS connections. There is no reported impact on integrity or availability. The flaw affects all supported Node.js release lines (22, 24, 26) and specific versions identified by Red Hat advisories.
Mitigation Recommendations
Red Hat has released security updates addressing this vulnerability in their Node.js packages. Users should apply the relevant updates from Red Hat advisories (e.g., RHSA-2026:39246) to remediate the issue. Since this is not a cloud service, remediation requires updating the affected Node.js versions. Patch status is confirmed via Red Hat advisories. No vendor advisory indicates that no action is required; therefore, applying the official patches is recommended.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- hackerone
- Date Reserved
- 2026-05-22T15:00:09.276Z
- Cvss Version
- 3.0
- State
- PUBLISHED
- Remediation Level
- null
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-48618","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:39246","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:35842","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:35841","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:35892","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:35891","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:9455","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:28727","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:29012","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:7378","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:30172","vendor":"Red Hat"}]
Threat ID: 6a3dd65f4853345fc1fa2e22
Added to database: 06/26/2026, 01:31:11 UTC
Last enriched: 07/22/2026, 22:32:47 UTC
Last updated: 08/09/2026, 00:41:15 UTC
Views: 193
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.