| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Node.js up to 22.22.3/24.16.0/26.3.0. It has been rated as critical. This affects an unknown part. This manipulation causes access control. This vulnerability is handled as CVE-2026-48930. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in Node.js up to 22.22.3/24.16.0/26.3.0. It has been declared as critical. Affected by this vulnerability is an unknown function. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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**.
The advisory is shared at nodejs.org. This vulnerability is known as CVE-2026-48930 since 05/26/2026. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
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). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 22.22.0
- 22.22.1
- 22.22.2
- 22.22.3
- 24.0
- 24.1
- 24.2
- 24.3
- 24.4
- 24.5
- 24.6
- 24.7
- 24.8
- 24.9
- 24.10
- 24.11
- 24.12
- 24.13
- 24.14
- 24.15
- 24.16.0
- 26.0
- 26.1
- 26.2
- 26.3.0
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.6
CNA Vector (hackerone): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 323047
Nessus Name: SUSE SLES15 Security Update : nodejs24 (SUSE-SU-2026:2633-1)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Node.js 22.23.0/24.17.0/26.3.1
Timeline
05/26/2026 CVE reserved06/26/2026 Advisory disclosed
06/26/2026 VulDB entry created
07/15/2026 VulDB entry last update
Sources
Advisory: nodejs.orgStatus: Confirmed
CVE: CVE-2026-48930 (🔒)
GCVE (CVE): GCVE-0-2026-48930
GCVE (VulDB): GCVE-100-374101
Entry
Created: 06/26/2026 07:39Updated: 07/15/2026 16:37
Changes: 06/26/2026 07:39 (61), 06/27/2026 01:56 (2), 07/15/2026 16:34 (2), 07/15/2026 16:37 (6)
Complete: 🔍
Committer: lywand
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.