Node.js up to 22.22.3/24.16.0/26.3.0 unicode encoding

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.1$0-$5k0.00

Summaryinfo

A vulnerability has been found in Node.js up to 22.22.3/24.16.0/26.3.0 and classified as problematic. This impacts an unknown function. Performing a manipulation results in improper handling of unicode encoding. This vulnerability is reported as CVE-2026-48618. The attack is possible to be carried out remotely. No exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Node.js up to 22.22.3/24.16.0/26.3.0. This affects an unknown part. The manipulation with an unknown input leads to a improper handling of unicode encoding vulnerability. CWE is classifying the issue as CWE-176. The product does not properly handle when an input contains Unicode encoding. This is going to have an impact on confidentiality. The summary by CVE is:

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**.

The advisory is shared at nodejs.org. This vulnerability is uniquely identified as CVE-2026-48618 since 05/22/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 323047 (SUSE SLES15 Security Update : nodejs24 (SUSE-SU-2026:2633-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 22.23.0, 24.17.0 or 26.3.1 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (323047). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.2
VulDB Meta Temp Score: 6.1

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 6.5
NVD Vector: 🔒

CNA Base Score: 7.7
CNA Vector (hackerone): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Improper handling of unicode encoding
CWE: CWE-176 / CWE-172
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 323047
Nessus Name: SUSE SLES15 Security Update : nodejs24 (SUSE-SU-2026:2633-1)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Node.js 22.23.0/24.17.0/26.3.1

Timelineinfo

05/22/2026 CVE reserved
06/26/2026 +35 days Advisory disclosed
06/26/2026 +0 days VulDB entry created
07/17/2026 +21 days VulDB entry last update

Sourcesinfo

Advisory: nodejs.org
Status: Confirmed

CVE: CVE-2026-48618 (🔒)
GCVE (CVE): GCVE-0-2026-48618
GCVE (VulDB): GCVE-100-374097

Entryinfo

Created: 06/26/2026 07:38
Updated: 07/17/2026 16:17
Changes: 06/26/2026 07:38 (60), 06/27/2026 01:56 (2), 07/15/2026 16:35 (2), 07/15/2026 16:37 (6), 07/17/2026 16:17 (12)
Complete: 🔍
Committer: lywand
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!