CVE-2026-48618: A flaw in Node.js TLS hostname handling can cause Node.js unicode dot separator handling can lead to tls wildc
CVE-2026-48618 is a medium-severity flaw (CVSS 6.5) affecting node.js. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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**.
Why this priority
- No elevated risk signals yet
No fix is published yet: follow the downgrade or mitigation steps.
Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Advisories and coverage
Official advisories
- AlmaLinux Errata: [ALSA-2026:35891] Important: nodejs:24 security, bug fix, and enhancement update 2026-07-07
- AlmaLinux Errata: [ALSA-2026:35892] Important: nodejs:22 security, bug fix, and enhancement update 2026-07-07
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-48618?
node.js: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2026-48618 being exploited?
CVE-2026-48618 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-48618 affect?
CVE-2026-48618 affects node.js. Severity is medium (CVSS 6.5). 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 im
How urgent is CVE-2026-48618?
Priority 45/100. No elevated risk signals yet.
Software pages
Related CVEs
- CVE-2026-48937 HIGH 7.5 UPGRADE A flaw in Node.js HTTP/2 server API can cause servers to keep accepting data even after sending a `GOAWAY` fra
- CVE-2026-48931 LOW 3.7 DOWNGRADE A flaw in Node.js HTTP Agent can cause a client to accept as valid a response that is send before the client h
- CVE-2026-48933 HIGH 7.5 DOWNGRADE A flaw in Node.js WebCrypto implementation can crash the process if the input of `subtle.encrypt()` is a multi
- CVE-2026-48930 CRITICAL 9.8 DOWNGRADE A flaw in Node.js TLS hostname handling can cause Embedded-nul hostnames can lead to silent authority rebindin
- CVE-2026-48619 HIGH 7.5 DOWNGRADE A flaw in Node.js HTTP/2 client allows a server to send an unlimited number of ORIGIN frames, which could lead