How severe is CVE-2026-48618?

CVE-2026-48618 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2026-48618 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (48th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-48618?

CVE-2026-48618 primarily affects Nodejs Node.js. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2026-48618?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-48618 have an EU (EUVD) identifier?

Yes. CVE-2026-48618 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-39610.

When was CVE-2026-48618 published?

CVE-2026-48618 was published on 2026-06-26.

CVE-2026-48618

CVE-2026-48618 is a medium-severity vulnerability in Nodejs Node.js with a CVSS 3.x base score of 6.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-176.

Key facts

Severity: Medium (CVSS 3.x base score 6.5)
EPSS exploit prediction: 1% (48th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-39610
Weakness: CWE-176
Affected product: Nodejs Node.js
Published: 2026-06-26
Last modified: 2026-06-26

Description

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

Frequently asked questions

What is CVE-2026-48618?: 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**.
How severe is CVE-2026-48618?: CVE-2026-48618 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-48618 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (48th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-48618?: CVE-2026-48618 primarily affects Nodejs Node.js. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2026-48618?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-48618 have an EU (EUVD) identifier?: Yes. CVE-2026-48618 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-39610.
When was CVE-2026-48618 published?: CVE-2026-48618 was published on 2026-06-26.

References

https://nodejs.org/en/blog/vulnerability/june-2026-security-releases

Affected products (3)

cpe:2.3:a:nodejs:node.js:22.22.3:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:24.16.0:*:*:*:-:*:*:*
cpe:2.3:a:nodejs:node.js:26.3.0:*:*:*:-:*:*:*

More vulnerabilities in Nodejs Node.js

CVE-2026-21636 — Critical (CVSS 10.0): A flaw in Node.js's permission model allows Unix Domain Socket (UDS) connections to bypass network restrictions when…
CVE-2015-0278 — Critical (CVSS 10.0): libuv before 0.10.34 does not properly drop group privileges, which allows context-dependent attackers to gain…
CVE-2026-48930 — Critical (CVSS 9.8): A flaw in Node.js TLS hostname handling can cause Embedded-nul hostnames can lead to silent authority rebinding due to…
CVE-2024-3566 — Critical (CVSS 9.8): A command inject vulnerability allows an attacker to perform command injection on Windows applications that indirectly…
CVE-2024-21896 — Critical (CVSS 9.8): The permission model protects itself against path traversal attacks by calling path.resolve() on any paths given by the…
CVE-2023-39332 — Critical (CVSS 9.8): Various `node:fs` functions allow specifying paths as either strings or `Uint8Array` objects. In Node.js environments,…

All CVEs affecting Nodejs Node.js →

Other CWE-176 vulnerabilities

CVE-2025-71316 — Critical (CVSS 9.8): SQLite 'sqldiff.exe' does not securely handle the way the Microsoft Windows C runtime converts Unicode characters to…
CVE-2024-24691 — Critical (CVSS 9.6): Improper input validation in Zoom Desktop Client for Windows, Zoom VDI Client for Windows, and Zoom Meeting SDK for…
CVE-2026-23950 — High (CVSS 8.8): node-tar,a Tar for Node.js, has a race condition vulnerability in versions up to and including 7.5.3. This is due to an…
CVE-2024-43093 — High (CVSS 7.3): In shouldHideDocument of ExternalStorageProvider.java, there is a possible bypass of a file path filter designed to…
CVE-2026-4116 — High (CVSS 7.2): Improper handling of Unicode encoding in SonicWall SMA1000 series appliances allows a remote authenticated SSLVPN user…
CVE-2026-20202 — Medium (CVSS 6.6): In Splunk Enterprise versions below 10.2.2, 10.0.5, 9.4.10, and 9.3.11, and Splunk Cloud Platform versions below…

Browse all CWE-176 vulnerabilities →