Bug 2493337 (CVE-2026-48618) - CVE-2026-48618 nodejs: Node.js: Authentication bypass due to TLS hostname handling and unicode dot separator mismatch
Summary: CVE-2026-48618 nodejs: Node.js: Authentication bypass due to TLS hostname han...
Keywords:
Status: NEW
Alias: CVE-2026-48618
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2493808 2493810 2493811
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-26 02:02 UTC by OSIDB Bzimport
Modified: 2026-08-10 02:41 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:35841 0 None None None 2026-07-06 04:37:08 UTC
Red Hat Product Errata RHSA-2026:35842 0 None None None 2026-07-06 05:16:32 UTC
Red Hat Product Errata RHSA-2026:35891 0 None None None 2026-07-06 14:23:27 UTC
Red Hat Product Errata RHSA-2026:35892 0 None None None 2026-07-06 14:45:17 UTC
Red Hat Product Errata RHSA-2026:39246 0 None None None 2026-07-14 12:31:12 UTC
Red Hat Product Errata RHSA-2026:39868 0 None None None 2026-07-15 11:23:37 UTC
Red Hat Product Errata RHSA-2026:41947 0 None None None 2026-07-20 13:07:14 UTC
Red Hat Product Errata RHSA-2026:52399 0 None None None 2026-08-10 02:41:10 UTC

Description OSIDB Bzimport 2026-06-26 02:02:34 UTC 
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**.
Comment 2 errata-xmlrpc 2026-07-06 04:37:07 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:35841 https://access.redhat.com/errata/RHSA-2026:35841
Comment 3 errata-xmlrpc 2026-07-06 05:16:31 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:35842 https://access.redhat.com/errata/RHSA-2026:35842
Comment 4 errata-xmlrpc 2026-07-06 14:23:26 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:35891 https://access.redhat.com/errata/RHSA-2026:35891
Comment 5 errata-xmlrpc 2026-07-06 14:45:15 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:35892 https://access.redhat.com/errata/RHSA-2026:35892
Comment 6 errata-xmlrpc 2026-07-14 12:31:11 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10.0 Extended Update Support

Via RHSA-2026:39246 https://access.redhat.com/errata/RHSA-2026:39246
Comment 7 errata-xmlrpc 2026-07-15 11:23:36 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:39868 https://access.redhat.com/errata/RHSA-2026:39868
Comment 8 errata-xmlrpc 2026-07-20 13:07:13 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:41947 https://access.redhat.com/errata/RHSA-2026:41947
Comment 9 errata-xmlrpc 2026-08-10 02:41:09 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.6 Extended Update Support

Via RHSA-2026:52399 https://access.redhat.com/errata/RHSA-2026:52399
Note You need to log in before you can comment on or make changes to this bug.