CVE-2023-6401 is an uncontrolled search path vulnerability affecting an unspecified functionality associated with dbghelp.exe in NotePad++ through version 8.1. Manipulation of the search path can cause the application to resolve files from an uncontrolled location. Exploitation is described as requiring local access.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a proof-of-concept (PoC) exploit for CVE-2023-6401, a DLL hijacking vulnerability affecting Notepad++ versions 8.1 and earlier on Windows. The exploit consists of a single C source file (dbghelp.c) that, when compiled as dbghelp.dll and placed in the Notepad++ application directory, will be loaded by Notepad++ on startup. Upon loading, the DLL executes arbitrary code (launches calc.exe and displays a message box) and then loads the legitimate dbghelp.dll from the system directory, forwarding API calls to maintain normal application behavior. The exploit demonstrates the risk of DLL search order hijacking when an attacker can write to the application directory. The repository includes a detailed README with usage instructions, compilation steps, and cleanup procedures. No network endpoints are involved; the attack vector is local, requiring filesystem access to the target directory.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.