CVE intelligence and bounded remediation
CVE-2026-48618 — Nodejs Node.Js security vulnerability
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**.
- Severity
- High
- CVSS
- 7.7 (3.1)
- Published
- 2026-06-26
- CISA KEV
- Not currently listed
- Ecosystem
- javascript/npm
- Weaknesses
- CWE-176, CWE-289
Affected products
- nodejs / node.js / 22.22.3
- nodejs / node.js / 24.16.0
- nodejs / node.js / 26.3.0
Matched remediation archetype
Authentication bypass and missing authentication
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Map every affected endpoint and protocol path, including alternate ports, legacy routes, recovery flows, service accounts, and machine-to-machine access.
- Confirm which deployments enable the affected authentication mode and whether the interface is reachable from untrusted networks.
- Review session, token, credential, and proxy trust configuration without attempting account takeover.
Remediate safely
- Apply the supported fix and centralize fail-closed authentication before protected request handling.
- Remove default or embedded credentials, rotate affected secrets and sessions, and bind authentication decisions to the intended audience and channel.
- Add negative tests for alternate routes, malformed or absent credentials, recovery flows, and proxy-derived identity.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.