CVE-2025-56383: Notepad++ · Uncontrolled Search Path Element
Source CVE Database V5
Not known to be exploited · CVSS 8.4 High.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
To mitigate this vulnerability, organizations should ensure that Notepad++ is installed only in directories with strict access controls, preventing write permissions for unprivileged users. Review and harden file system permissions on all directories containing executable files and DLLs related to Notepad++. Avoid installing Notepad++ in shared or user-writable locations such as temporary folders or network shares with lax permissions. Employ application whitelisting and integrity monitoring to detect unauthorized DLL modifications. Users should monitor for updates from Notepad++ developers and apply patches promptly once available. Additionally, consider running Notepad++ with the least privilege necessary and educate users about the risks of installing software in insecure locations. Network segmentation and endpoint protection solutions can further reduce the risk of lateral movement if exploitation occurs.
Description
Notepad++ v8.8.3 has a DLL hijacking vulnerability, which can replace the original DLL file to execute malicious code. NOTE: this is disputed by multiple parties because the behavior only occurs when a user installs the product into a directory tree that allows write access by arbitrary unprivileged users.
References
- github.com/notepad-plus-plus/notepad-plus-plus (opens in a new tab)
- github.com/zer0t0/CVE-2025-56383-Proof-of-Concept (opens in a new tab)
- github.com/zer0t0/CVE-2025-56383-Proof-of-Concept/issues/1 (opens in a new tab)
- vicarius.io/vsociety/posts/cve-2025-56383-detect-notepad-vulnerability (opens in a new tab)
- vicarius.io/vsociety/posts/cve-2025-56383-mitigate-notepad-vulnerability (opens in a new tab)