# CVE-2026-48800: Notepad++: Arbitrary Code Execution via shortcuts.xml UserCommand Injection

> Attackers can execute arbitrary code by injecting malicious commands into the shortcuts.xml file, which are then executed when the user selects the corresponding menu item.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Jun 2026
- **Updated:** 30 Jun 2026
- **Also known as:** GHSA-3x3f-3j39-pj3v

## What is CVE-2026-48800?

CVE-2026-48800 is a high-severity command injection vulnerability in notepad-plus-plus, published on 26 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Notepad++ is a free and open-source source code editor. Prior to 8.9.6.1, the <Command> tag text content inside <UserDefinedCommands> in shortcuts.xml is read by NppXml::value(aNode) (Parameters.cpp:3658) in the feedUserCmds() function and stored in UserCommand._cmd without any validation. When the user clicks the corresponding entry in the Run menu, NppCommands.cpp:4264 creates a Command object with string2wstring(ucmd.getCmd()) and calls run(), which invokes ShellExecute (RunDlg.cpp:221) with the attacker-controlled string as the executable path. The injected command appears as a normal menu item in the Run menu, making it a viable persistence mechanism.  This vulnerability is fixed in 8.9.6.1.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-48800?

It affects 1 product.


Products: Notepad-Plus-Plus Notepad\+\+.

## How do I fix CVE-2026-48800?

No fix has been published for CVE-2026-48800 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-48800 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48800 exists.

Public exploit code:

- https://github.com/kavin-jindal/CVE-2026-48800-PoC (github_poc): https://github.com/kavin-jindal/CVE-2026-48800-PoC

## Other vulnerabilities in notepad-plus-plus

- [CVE-2025-15556](https://insights.sbomify.com/CVE-2025-15556/): Notepad++ Download of Code Without Integrity Check (high 7.7, exploited in the wild)
- [CVE-2026-48778](https://insights.sbomify.com/CVE-2026-48778/): Notepad++: Arbitrary Code Execution via config.xml commandLineInterpreter (high 7.8)
- [CVE-2026-52884](https://insights.sbomify.com/CVE-2026-52884/): Notepad++: CVE-2026-48800 Bypass (high 7.8)
- [CVE-2023-47452](https://insights.sbomify.com/CVE-2023-47452/): Privilege escalation in n/a (high 7.8)
- [CVE-2023-40031](https://insights.sbomify.com/CVE-2023-40031/): Notepad++ vulnerable to heap buffer write overflow in Utf8_16_Read::convert (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48800 and fix it if it is affected.

What it is: CVE-2026-48800 is a high-severity command injection vulnerability in notepad-plus-plus, published on 26 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48800 exists.

Affected product: notepad-plus-plus. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48800/ (Markdown: https://insights.sbomify.com/CVE-2026-48800/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48800
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48800
- OSV: https://osv.dev/vulnerability/CVE-2026-48800

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48800/
Summaries are generated and may contain mistakes; the official description above is the record.