# CVE-2026-85995: Notepad++: Authenticode verification bypass allows modified updater execution

> Attackers can bypass Authenticode verification to execute modified updater code in Notepad++, requiring local file replacement privileges.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-cx87-7hhq-m2j3

## What is CVE-2026-85995?

CVE-2026-85995 is a high-severity vulnerability in notepad-plus-plus, published on 22 Sep 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. From 8.9.7 until 8.9.8, the Notepad++ updater and signature verification path can accept a modified GUP.exe file whose embedded certificate metadata remains present even though its Authenticode digest is invalid. An attacker who can replace or plant the updater-related file can cause Notepad++ to launch attacker-modified code when a user triggers the updater path, but the issue does not provide remote code execution by itself. This issue is fixed in version 8.9.8.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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


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

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

## Is CVE-2026-85995 being exploited?

There is no known exploitation of CVE-2026-85995 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85995 is a high-severity vulnerability in notepad-plus-plus, published on 22 Sep 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: There is no known exploitation of CVE-2026-85995 in the wild and no public exploit code.

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-85995/ (Markdown: https://insights.sbomify.com/CVE-2026-85995/index.md)
```

## Sources

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

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