CVE-2026-6539
Notepad-Plus-Plus Notepad\+\+ 8.9.3
Raw vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-6539 is a medium-severity Use of Externally-Controlled Format String (CWE-134) vulnerability in Notepad-Plus-Plus Notepad\+\+. Its CVSS base score is 4.6 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Malicious File (T1204.002); ranked at the 9th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-3 (Malicious Code Protection) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-26436
Vulnerability Data
Notepad++ 8.9.3 contains a format string injection vulnerability in the Find Results panel handler that allows attackers to cause denial of service and information disclosure by crafting a malicious nativeLang.xml language pack file. Attackers can distribute a poisoned language pack…
more
through community channels that triggers format string interpretation when a user performs search operations, leading to access violations and potential leakage of stack or register contents.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Vulnerability is triggered by user loading a crafted malicious nativeLang.xml language pack file, directly enabling exploitation via malicious file execution.
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
Mitigating Controls (NIST 800-53 r5) AI
Directly blocks exploitation of the externally-controlled format string in nativeLang.xml by requiring validation/sanitization of all inputs before they reach the Find Results panel handler.
Requires integrity verification of language-pack files before loading, preventing a poisoned nativeLang.xml from being interpreted as trusted input.
Treats the malicious language pack as untrusted code/content and applies scanning or execution restrictions before the format-string payload can be processed during search operations.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect format-string vulnerabilities before release.
Secure SDLC mandates input validation and safe API usage that can prevent externally-controlled format strings.
Application security requirements can specify safe formatting functions and ban uncontrolled format strings.
Secure architecture principles discourage dangerous string-handling patterns that lead to format-string issues.
Secure coding standards directly forbid the use of untrusted format strings and prescribe safe alternatives.