Vulnerability in launch-editor (CVE-2026-53632)
Summary
Vulnerability in launch-editor (CVE-2026-53632). Risk of unauthorized operations or information disclosure. Exploitable via smbserver.py. Mitigation: upgrade to 2.14.1 or later.
Original description
The description as published by the source.
launch-editor allows users to open files with line numbers in editor from Node.js. Prior to 2.14.1, the launch-editor NPM package accesses arbitrary paths including Windows UNC paths. When a UNC path is opened, Windows automatically attempts NTLM authentication to the remote host, causing the user’s NTLMv2 password hash to be leaked to an attacker-controlled SMB server. This can result in credential compromise through offline hash cracking. This vulnerability is fixed in 2.14.1.
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-53632 has been found in launch-editor.
Attackers can target a specific entry point like smbserver.py over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade launch-editor to 2.14.1 or later.
If unsure, ask your IT team or search "launch-editor CVE-2026-53632" on the vendor's site.
CVE-2026-53632 (launch-editor) — CWE-522
Attack surface: smbserver.py / vite / curl
Patched: 2.14.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-522) exists in launch-editor. Attackers reach the vulnerable code path via smbserver.py.
Check the vendor advisory for the affected versions of launch-editor. Attack surface: smbserver.py / vite / curl.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.14.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 'launch-editor' . 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 'launch-editor' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
launch-editorを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade launch-editor to 2.14.1ステージング環境で 2.14.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com