CVE-2026-48618
MEDIUMEPSS 87th pctlDescription
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**.
How to fix
This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Exploit Intelligence
Elevated risk: more likely to be exploited than 87% of all known CVEs.
References
Related Vulnerabilities
Other CWE-176 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-24691 | Critical | 9.6 | 1.7% | - | Fix |
| CVE-2023-39213 | Critical | 9.6 | 1.4% | - | Fix |
| CVE-2024-47611 | Unscored | - | 0.8% | - | - |
| CVE-2024-43093 | High | 7.3 | 0.7% | KEV | - |
| CVE-2026-45135 | High | 8.1 | 0.7% | - | Fix |
| CVE-2006-10002 | Medium | 7.5 | 0.6% | - | Fix |
Common questions
How do I fix CVE-2026-48618?
Published advisories record a fix for 57 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-48618 being actively exploited?
Not that we know of. CVE-2026-48618 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 3.2% is the estimated probability that it will be exploited in the next 30 days. That is higher than 87% of all scored CVEs.
How severe is CVE-2026-48618?
CVE-2026-48618 has a CVSS v3 base score of 6.5, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-48618 affect?
Published advisories record a fix for nodejs (Debian), nodejs (Rocky), nodejs (Red Hat / RHEL), nodejs-debuginfo (Red Hat / RHEL), and 53 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-48618
Markdown
[](https://tridentstack.com/cve/CVE-2026-48618)HTML
<a href="https://tridentstack.com/cve/CVE-2026-48618"><img src="https://tridentstack.com/cve/badge/CVE-2026-48618.svg" alt="CVE-2026-48618"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-10.