High [CVE-2026-48618] Authentication bypass due to TLS hostname handling and unicode dot separator mismatch
This high-severity Red Hat Linux advisory covers CVE-2026-48618 affecting Red Hat Enterprise Linux 10.0 Extended Update Support, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9.6 Extended Update Support.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
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**. A flaw was found in Node.js.
This flaw involves a mismatch in how Node.js handles TLS (Transport Layer Security) hostnames and unicode dot separators during authentication. An attacker could exploit this to bypass intended security boundaries, potentially leading to unauthorized access and confidentiality impact.
The issue affects Node.js versions 22, 24, and 26 as shipped in Red Hat products. Red Hat severity: Important — CVSS 7.7 (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N).
Weakness: CWE-289. Affected Red Hat products: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 10.0 Extended Update Support; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9; Red Hat Enterprise Linux 9.6 Extended Update Support; Red Hat Hardened Images.
Affected products named by the advisory: Red Hat package: nodejs24; Red Hat package: nodejs22.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 12 days ago·verify at source
- nodejs24-1:24.18.0-1.el10_2
- nodejs22-1:22.23.1-2.el10_2
- nodejs22-1:22.23.1-2.el10_0
- nodejs:24-8100020260630152626.6d880403
- nodejs:22-8100020260703140402.6d880403
- nodejs:24-9080020260626074955.rhel9
- nodejs:22-9080020260626075442.rhel9
- nodejs:22-9060020260804140259.rhel9
- nodejs22-main-22.23.1-1.hum1
- nodejs24-main-24.18.0-0.1.hum1
- nodejs26-main-26.4.0-1.2.hum1
- nodejs25-main-25.9.0-1.1.hum1
- nodejs20-main-20.20.2-1.hum1
- RHSA-2026:35841
- RHSA-2026:35842
- RHSA-2026:39246
- RHSA-2026:39868
- RHSA-2026:41947
- RHSA-2026:35891
- RHSA-2026:35892
- RHSA-2026:52399
- RHSA-2026:28727
- RHSA-2026:29012
- RHSA-2026:30172
- RHSA-2026:7378
- RHSA-2026:9455
Official advisory · high-confidence parse· fetched 12 days ago·verify at source
Mitigation checklist
- Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Official advisory · high-confidence parse· fetched 12 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.