CVE-2026-48930
Analyzed Analyzed - Analysis Complete

TLS Hostname Handling Flaw in Node.js

Publication date: 2026-06-26

Last updated on: 2026-06-26

Assigner: HackerOne

Description
A flaw in Node.js TLS hostname handling can cause Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver bindings. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-26
Last Modified
2026-06-26
Generated
2026-07-17
AI Q&A
2026-06-26
EPSS Evaluated
2026-07-16
NVD
CVE-2026-48930
EUVD
EUVD-2026-39614

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
nodejs node.js 26.3.0
nodejs node.js 24.16.0
nodejs node.js 22.22.3

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-284 The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a flaw in Node.js's TLS hostname handling where embedded null characters in hostnames can cause silent authority rebinding. This happens due to c-string truncation in resolver bindings, meaning the hostname string is cut off prematurely, potentially allowing an attacker to manipulate the hostname verification process.

Impact Analysis

The impact of this vulnerability includes the possibility of an attacker silently rebinding authority during TLS hostname verification. This can lead to compromised integrity and confidentiality of communications, as the attacker might redirect or intercept secure connections without detection.

Compliance Impact

The provided information does not specify how the Node.js TLS hostname handling vulnerability (CVE-2026-48930) impacts compliance with common standards and regulations such as GDPR or HIPAA.

Mitigation Strategies

The vulnerability affects all supported Node.js release lines: 22, 24, and 26. To mitigate this vulnerability, users should update Node.js to the latest patched versions where the issue has been fixed.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-48930. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart