How severe is CVE-2026-48618?

CVE-2026-48618 has a CVSS score of 7.7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-48618?

Affected package information for CVE-2026-48618 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2026-48618?

No fixed release is recorded for CVE-2026-48618 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2026-48618 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2026-48618 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2026-48618 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-48618 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-48618?

CVE-2026-48618 has an EPSS (Exploit Prediction Scoring System) score of 3.2%, placing it in the 88th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-48618?

CVE-2026-48618 is classified as CWE-176 (CWE-176), CWE-289 (CWE-289). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-48618 published, and has it been updated?

CVE-2026-48618 was published on June 26, 2026 and was last updated on September 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

Not in CISA KEV

HIGH severity

CVE-2026-48618 — node

HIGH

CVE-2026-48618 is a high-severity (CVSS 7.7) CWE-176 vulnerability. No vendor fix is recorded yet; mitigation options are listed below.

Also known asBIT-node-2026-48618BIT-node-min-2026-48618

Published

Jun 26, 2026

Updated

Sep 29, 2026

Affected

1 product

Patched

See advisory

Exploits

None indexed

Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-48618.

EPSS Exploitation Probability

via FIRST.org ↗

3.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-48618 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Description

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.

Affected Products

1 product · 3 configurations

Application

node.jsnodejs

3 versions

22.22.324.16.026.3.0

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2026-48618 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This Important flaw in Node.js allows for a TLS wildcard-depth authentication bypass due to a mismatch in how hostnames and unicode dot separators are handled during authentication. This could enable an attacker to circumvent security boundaries, potentially leading to unauthorized access and compromise of sensitive…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for CVE-2026-48618 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Enterprise Linux 10	`nodejs24-1:24.18.0-1.el10_2`	RHSA-2026:35841
Red Hat Enterprise Linux 10	`nodejs22-1:22.23.1-2.el10_2`	RHSA-2026:35842
Red Hat Enterprise Linux 10.0 Extended Update Support	`nodejs22-1:22.23.1-2.el10_0`	RHSA-2026:39246
Red Hat Enterprise Linux 8	`nodejs:24-8100020260630152626.6d880403`	RHSA-2026:39868
Red Hat Enterprise Linux 8	`nodejs:22-8100020260703140402.6d880403`	RHSA-2026:41947
Red Hat Enterprise Linux 9	`nodejs:24-9080020260626074955.rhel9`	RHSA-2026:35891
Red Hat Enterprise Linux 9	`nodejs:22-9080020260626075442.rhel9`	RHSA-2026:35892
Red Hat Enterprise Linux 9.6 Extended Update Support	`nodejs:22-9060020260804140259.rhel9`	RHSA-2026:52399

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2026-48618 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works