Skip to main content
No exploitation reportedFix available

CVE-2026-48618

No exploitation reported by the sources we read.

  • Published2026-06-26
  • WeaknessCWE-176 · CWE-289

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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

Timeline

dates in UTC
  1. 2026-06-2602:16CVE publishedNVD

Versions per branch

NVD · OSV
Node.js
BranchAffectedFixed in
22.22= 22.22.3no fix published
24.16= 24.16.0no fix published
26.3= 26.3.0no fix published
node
BranchAffectedFixed in
26.3≥ 26.3.0, < 26.3.126.3.1
24.x≥ 24.16.0, < 24.17.024.17.0
22.x≥ 22.22.3, < 22.23.022.23.0
node-min
BranchAffectedFixed in
26.3≥ 26.3.0, < 26.3.126.3.1
24.x≥ 24.16.0, < 24.17.024.17.0
22.x≥ 22.22.3, < 22.23.022.23.0

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As hackerone, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • nodejs nodeother versions: not affected
    Affected
    • ≥ 22.22.3, ≤ 22.22.3no fix statedsemver
    • ≥ 24.16.0, ≤ 24.16.0no fix statedsemver
    • ≥ 26.3.0, ≤ 26.3.0no fix statedsemver

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-06-26

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • bunopenSUSE:Tumbleweedall versions · fixed in 1.4.4-1.1
  • nodejsUbuntu:Pro:22.04:LTSall versions · no fixed version listed
  • nodejsUbuntu:Pro:20.04:LTSall versions · no fixed version listed
  • nodejsUbuntu:Pro:18.04:LTSall versions · no fixed version listed
  • nodejsUbuntu:Pro:16.04:LTSall versions · no fixed version listed
  • nodejsUbuntu:Pro:14.04:LTSall versions · no fixed version listed
  • nodejsUbuntu:26.10all versions · no fixed version listed
  • nodejsUbuntu:26.04:LTSall versions · no fixed version listed

162 more package ranges on OSV.dev

Vendor advisories

  • CVE-2026-48618 Red Hat Product Security401 products fixed · 7 known affected

    nodejs: Node.js: Authentication bypass due to TLS hostname handling and unicode dot separator mismatch

    nodejs26.src as a component of Red Hat Enterprise Linux 10 · nodejs-docs (nodejs:26) as a component of Red Hat Enterprise Linux 9 · nodejs-full-i18n (nodejs:26) as a component of Red Hat Enterprise Linux 9 · +4 more

  • RHSA-2026:98619 Red Hat Product Security31 products fixed

    Red Hat Security Advisory: nodejs26 security, bug fix, and enhancement update

  • RHSA-2026:97855 Red Hat Product Security40 products fixed

    Red Hat Security Advisory: nodejs:26 security update

  • RHSA-2026:52399 Red Hat Product Security43 products fixed

    Red Hat Security Advisory: nodejs:22 security update

  • RHSA-2026:41947 Red Hat Product Security43 products fixed

    Red Hat Security Advisory: nodejs:22 security, bug fix, and enhancement update

  • RHSA-2026:39868 Red Hat Product Security40 products fixed

    Red Hat Security Advisory: nodejs:24 security, bug fix, and enhancement update

10 more advisories

Full record on NVD

Fix

  1. Vendor fix Red Hat Product Security RHSA-2026:98619 · 31 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
  2. Vendor fix Red Hat Product Security CVE-2026-48618 · 17 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
  3. Workaround from the vendor Red Hat Product Security RHSA-2026:98619 · 31 productsMitigation 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.

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionnone2026-06-26
  • CNACVSS 3.17.7known since 2026-10-26
  • NVDCVSS 3.16.5read 2026-10-26
  • CNACVSS 3.07.7known since 2026-10-26
  • CNAweakness (CWE)CWE-176, CWE-289known since 2026-10-26
  • FIRST EPSSEPSS score3.1 %2026-11-18
  • OSVaffected packages—
  • GitHub Advisoriesadvisory—

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Published
2026-06-26
Last Modified
2026-10-25
NVD status
Modified
GitHub Advisory
GHSA-g57m-hr98-5m89

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

Is CVE-2026-48618 actively exploited?

Active exploitation of CVE-2026-48618 has not been confirmed. Its EPSS score was 3.1% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

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

CVE-2026-48618 has a CVSS v3 base score of 6.5 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.

Running Node.js? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record