Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-48618 medium CVSS 6.5

Vulnerability in Node.js TLS hostname handling (CVE-2026-48618)

Summary

Vulnerability in Node.js TLS hostname handling (CVE-2026-48618). Confidential information can be exposed externally.

Original description

The description as published by the source.

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.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-48618 has been found in Node.js TLS hostname handling.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Node.js TLS hostname handling CVE-2026-48618" on the vendor's site.

CVE-2026-48618 (Node.js TLS hostname handling) — CWE-176 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-176) exists in Node.js TLS hostname handling.

📍 Affected scope

Check the vendor advisory for the affected versions of Node.js TLS hostname handling.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Node.js TLS hostname handling を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami node-min
[{"type":"SEMVER","events":[{"introduced":"22.22.3"},{"fixed":"22.23.0"},{"introduced":"24.16.0"},{"fixed":"24.17.0"},{"introduced":"26.3.0"},{"fixed":"26.3.1"}]}]
Bitnami node
[{"type":"SEMVER","events":[{"introduced":"22.22.3"},{"fixed":"22.23.0"},{"introduced":"24.16.0"},{"fixed":"24.17.0"},{"introduced":"26.3.0"},{"fixed":"26.3.1"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details