Vulnerability in Notepad (CVE-2026-52884)
Summary
Vulnerability in Notepad (CVE-2026-52884). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 8.9.6.2 or later.
Original description
The description as published by the source.
Notepad++ is a free and open-source source code editor. In v8.9.6.1, isInTrustedDirectory() does NOT canonicalize the path before checking. It uses a prefix-based check (PathIsPrefix() or equivalent) that matches paths starting with trusted directory strings. A path traversal using ....\ after a trusted directory prefix passes the check while resolving to an untrusted location. The CVE-2026-48800 patch adds isInTrustedDirectory() validation in Command::run() (RunDlg.cpp) before calling ShellExecute(). This function checks whether the resolved executable path is under a trusted directory. This vulnerability is fixed in 8.9.6.2.
Source: NIST National Vulnerability Database 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-52884 has been found in Notepad.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade Notepad to 8.9.6.2 or later.
If unsure, ask your IT team or search "Notepad CVE-2026-52884" on the vendor's site.
CVE-2026-52884 (Notepad) — CWE-42 / CVSS v3 7.8
Attack vector: local / unauthenticated
Patched: 8.9.6.2 — 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-42) exists in Notepad.
Check the vendor advisory for the affected versions of Notepad.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to 8.9.6.2.
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 'Notepad' . 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 'Notepad' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Notepadを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Notepad to 8.9.6.2ステージング環境で 8.9.6.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com