# CVE-2026-2040: PDF-XChange Editor TrackerUpdate Uncontrolled Search Path Element Local Privilege Escalation Vulnerability

> Local attackers can escalate privileges and execute code by exploiting an uncontrolled search path element in the TrackerUpdate process.

- **Severity:** High 7.3 (`CVSS:3.0/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:** 20 Feb 2026
- **Updated:** 24 Feb 2026
- **Also known as:** GHSA-9j8v-79v3-wcmp

## What is CVE-2026-2040?

CVE-2026-2040 is a high-severity vulnerability in PDF-XChange Editor, published on 20 Feb 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

PDF-XChange Editor TrackerUpdate Uncontrolled Search Path Element Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of PDF-XChange Editor. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability.

The specific flaw exists within the TrackerUpdate process. The product loads a library from an unsecured location. An attacker can leverage this vulnerability to escalate privileges and execute code in the context of a target user. Was ZDI-CAN-27788.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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


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

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

## Is CVE-2026-2040 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2040 is a high-severity vulnerability in PDF-XChange Editor, published on 20 Feb 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-2040 in the wild and no public exploit code.

Affected product: PDF-XChange Editor. 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-2040/ (Markdown: https://insights.sbomify.com/CVE-2026-2040/index.md)
```

## Sources

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

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