Loading vulnerability…
Notepad++ before 8.9.4 contains a format string injection vulnerability in the FindInFiles/Find Results handling path. According to the provided content, the issue is triggered when the nativeLang.xml language pack value for "find-result-hits" contains format specifiers such as "%s". When a user performs search operations, the application interprets attacker-controlled format tokens instead of treating them as literal text, causing crashes/access violations and potentially exposing process memory contents such as stack or register data. The issue was fixed in Notepad++ 8.9.4 and is associated with the patch referenced by issue #17960.
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 additional Notepad++ vulnerability referenced as being fixed in the same 8.9.4 patch, though technical details are not provided in the content.
A vulnerability associated with a crash in Notepad++ FindInFiles when nativeLang.xml's "find-result-hits" contains "%s".
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.