Loading vulnerability…
Notepad++ versions prior to 8.9.2 contain an Unsafe Search Path (CWE-426) issue when invoking Windows Explorer without specifying an absolute executable path. If an attacker can influence/control the process working directory at the time Notepad++ launches Explorer, Windows search-order resolution may cause a malicious attacker-supplied "explorer.exe" in that directory to be executed instead of the legitimate Windows Explorer binary, resulting in arbitrary code execution in the context of the Notepad++ process. The issue is fixed in Notepad++ 8.9.2.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An untrusted search path vulnerability in Notepad++ that could allow arbitrary code execution under specific conditions.
An untrusted search path vulnerability in Notepad++ that could allow arbitrary code execution under certain conditions.
An unsafe search path issue in Notepad++ where launching Windows Explorer without an absolute path could allow a malicious explorer.exe from a controlled working directory to be executed, leading to arbitrary code execution in the application's context.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.