Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-48618: A flaw in Node.js TLS hostname handling can cause Node.js unicode dot separator handling can lead to tls wildc

45
This month
MEDIUM 6.5DOWNGRADE

CVE-2026-48618 is a medium-severity flaw (CVSS 6.5) affecting node.js. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

  • No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score6.5 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance3.1% (top 12%)
CISA exploited listNo
WeaknessCWE-176, CWE-289
Published2026-06-26
Last modified2026-10-25
Publisher (CNA): HackerOne · Vendor: nodejs

Share: LinkedIn · X · Reddit

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

nodejs node.js DOWNGRADE
Affected: 22.22.3 · 24.16.0 · 26.3.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 22.22.3
1. Check installed version
apt-cache policy node.js || rpm -q node.js || node.js --version
2. No fixed release: DOWNGRADE to a release before 22.22.3 (Debian / Ubuntu)
apt-cache madison node.js sudo apt install node.js=<VERSION_BEFORE_22.22.3> sudo apt-mark hold node.js
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list node.js sudo dnf downgrade node.js-<VERSION_BEFORE_22.22.3> sudo dnf versionlock add node.js
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.

Advisories and coverage

Official advisories

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-48618?

node.js: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2026-48618 being exploited?

CVE-2026-48618 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-48618 affect?

CVE-2026-48618 affects node.js. Severity is medium (CVSS 6.5). 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 im

How urgent is CVE-2026-48618?

Priority 45/100. No elevated risk signals yet.

Software pages

Node.js vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.