Notepad++ Download of Code Without Integrity Check Vulnerability
notepad-plus-plus — notepad-plus-plus
Notepad++ versions prior to 8.8.9, when using the WinGUp updater, contain an update integrity verification vulnerability where downloaded update metadata and installers are not cryptographically verified. An attacker able to intercept or redirect update traffic can cause the updater to download and execute an attacker-controlled installer, resulting in arbitrary code execution with the privileges of the user.
7.5
1.7%
Vector breakdown
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
- Published
- Feb 3, 2026
- Modified
- Jun 17, 2026
- Added to KEV
- Feb 12, 2026
- Federal patch due
- Mar 5, 2026
CISA required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Weakness classification
Affected packages
Proof-of-concept & exploitation references
2 foundWeaponization
Public repositories whose name or description references CVE-2025-15556, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit - cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.
- George0Papasotiriou/CVE-2025-15556-Notepad-WinGUp-Updater-RCE★ 1
updated Feb 10, 2026
- renat0z3r0/notepadpp-supply-chain-iocs★ 1
IoCs and detection rules for the Notepad++ supply chain attack (CVE-2025-15556) — Lotus Blossom APT, June–December 2025. Includes Falcon LogScale queries, YARA/Sigma rules, and MITRE ATT&CK mapping.
updated Mar 3, 2026
References
Frequently asked questions
What is CVE-2025-15556?
Notepad++ versions prior to 8.8.9, when using the WinGUp updater, contain an update integrity verification vulnerability where downloaded update metadata and installers are not cryptographically verified. An attacker able to intercept or redirect update traffic can cause the updater to download and execute an attacker-controlled installer, resulting in arbitrary code execution with the privileges of the user.
How severe is CVE-2025-15556?
CVE-2025-15556 has a CVSS base score of 7.5 out of 10 (CVSS 3.1).
Is CVE-2025-15556 actively exploited in the wild?
Yes. CVE-2025-15556 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added Feb 12, 2026, meaning CISA has confirmed evidence of active exploitation.
What is the EPSS score for CVE-2025-15556?
1.7% - meaning FIRST.org's EPSS model estimates a 1.7% probability this vulnerability will be exploited in the wild within 30 days (76% percentile among all scored CVEs).
Is there exploit tooling available for CVE-2025-15556?
We found 2 public GitHub repositories referencing CVE-2025-15556, though none matched a known Nuclei template or Metasploit module at last check. Review each one before relying on it - see the proof-of-concept section above.
What type of vulnerability is CVE-2025-15556?
CVE-2025-15556 is classified under CWE-494 (CWE-494 Download of Code Without Integrity Check).
Cross-checked against
Impactr finds and proves whether CVE-2025-15556 - or flaws like it - are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.
Join the waitlist