CVE-2026-48618
mediumpriority · track · 27EPSS 0.032 · 88 %ileDEEUUSEPSS · scored 2026-10-23
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**.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 6–7.7
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (21)
Products and version ranges known to be affected.
advisories (4)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2026-2004Node.js: Mehrere SchwachstellenDeutsch2026-06-18csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in Node.js ausnutzen, um Sicherheitsvorkehrungen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.
- WID-SEC-W-2026-2919IBM App Connect Enterprise: Mehrere SchwachstellenDeutsch2026-08-18csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise ausnutzen, um beliebigen Programmcode auszuführen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen, und um Sicherheitsvorkehrungen zu umgehen.
- BIT-node-2026-486182026-06-29vendor · osvUS
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**.
- BIT-node-min-2026-486182026-06-29vendor · osvUS
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**.
also known as (5)
Other names and identifiers for this entity.
- CNNVD-2026-52153144cnnvd
- EUVD-2026-39610enisa_euvd
- GHSA-g57m-hr98-5m89enisa_euvd
- BIT-node-2026-48618osv
- BIT-node-min-2026-48618osv
sources
Which sources assert this record, and when.
references (19)
External citations — patches, advisories, analysis.
- https://nodejs.org/en/blog/vulnerability/june-2026-security-releasescnnvd
- https://nodejs.org/en/blog/vulnerability/june-2026-security-releasesenisa_euvd
- https://access.redhat.com/errata/RHSA-2026:28727nvd
- https://access.redhat.com/errata/RHSA-2026:29012nvd
- https://access.redhat.com/errata/RHSA-2026:30172nvd
- https://access.redhat.com/errata/RHSA-2026:35841nvd
- https://access.redhat.com/errata/RHSA-2026:35842nvd
- https://access.redhat.com/errata/RHSA-2026:35891nvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan