# CVE-2025-59866: Privilege escalation in DFMPro for CATIA

> A local attacker can overwrite installer executables due to insecure permissions, leading to privilege escalation and arbitrary code execution.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N`)
- **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:** 17 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-xrg7-hrrm-57fm

## What is CVE-2025-59866?

CVE-2025-59866 is a low-severity vulnerability in HCLSoftware DFMPro for CATIA, published on 17 Jul 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

The HCL DFMPro, DFXAnalytics and DFXServer installers are affected by ‘Insecure file permissions Leading to Privilege Escalation’ vulnerability, which enables any logged-in non-administrative user to overwrite or replace the executable file with a malicious binary.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2025-59866?


## How do I fix CVE-2025-59866?

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

## Is CVE-2025-59866 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59866 and fix it if it is affected.

What it is: CVE-2025-59866 is a low-severity vulnerability in HCLSoftware DFMPro for CATIA, published on 17 Jul 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-2025-59866 in the wild and no public exploit code.

Affected product: HCLSoftware DFMPro for CATIA. 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-2025-59866/ (Markdown: https://insights.sbomify.com/CVE-2025-59866/index.md)
```

## Sources

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

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