Vulnerability in node (CVE-2026-48936)
Summary
Vulnerability in node (CVE-2026-48936). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 26.3.1 or later.
Original description
The description as published by the source.
A flaw in Node.js Permission API can cause a local server to be started (via a Unix domain socket), even without the --allow-net permission.
This vulnerability affects one supported release line: 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-48936 has been found in node.
Risk of unauthorized operations or information disclosure. CVSS score: 3.3/10.
What to do: upgrade node to 26.3.1 or later.
If unsure, ask your IT team or search "node CVE-2026-48936" on the vendor's site.
CVE-2026-48936 (node) — CWE-284 / CVSS v3 3.3
Attack vector: local / no user interaction
Patched: 26.3.1 — apply immediately
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.
A vulnerability (CWE-284) exists in node.
Check the vendor advisory for the affected versions of node.
Severity: Low (CVSS 3.3/10). Risk of unauthorized operations or information disclosure.
Update to 26.3.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'node' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'node' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
nodeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade node to 26.3.1ステージング環境で 26.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- BellSoft Alpaquita BELL-CVE-2026-48936
- Ubuntu UBUNTU-CVE-2026-48936 nodejs
References
- advisory nodejs.org
- web nvd.nist.gov
- web github.com