# CVE-2025-65117: AVEVA Process Optimization Use of Potentially Dangerous Function

> An authenticated user can escalate privileges to a victim's identity by embedding malicious OLE objects in graphics, affecting AVEVA Process Optimization users.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Jan 2026
- **Updated:** 16 Jan 2026
- **Also known as:** GHSA-cvm5-pcmg-6888

## What is CVE-2025-65117?

CVE-2025-65117 is a high-severity vulnerability in AVEVA Process Optimization, published on 16 Jan 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 vulnerability, if exploited, could allow an authenticated miscreant 
(Process Optimization Designer User) to embed OLE objects into graphics,
 and escalate their privileges to the identity of a victim user who 
subsequently interacts with the graphical elements.

Weakness: CWE-676 (Use of Potentially Dangerous Function)

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

It affects 1 product.


Products: Aveva Process Optimization.

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

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

## Is CVE-2025-65117 being exploited?

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

## Other vulnerabilities in AVEVA Process Optimization

- [CVE-2025-61937](https://insights.sbomify.com/CVE-2025-61937/): AVEVA Process Optimization Code Injection (critical 10.0)
- [CVE-2025-61943](https://insights.sbomify.com/CVE-2025-61943/): AVEVA Process Optimization SQL Injection (critical 9.3)
- [CVE-2025-64691](https://insights.sbomify.com/CVE-2025-64691/): AVEVA Process Optimization Code Injection (critical 9.3)
- [CVE-2025-65118](https://insights.sbomify.com/CVE-2025-65118/): AVEVA Process Optimization Uncontrolled Search Path Element (critical 9.3)
- [CVE-2025-64729](https://insights.sbomify.com/CVE-2025-64729/): AVEVA Process Optimization Missing Authorization (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65117 is a high-severity vulnerability in AVEVA Process Optimization, published on 16 Jan 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-65117 in the wild and no public exploit code.

Affected product: AVEVA Process Optimization. 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-65117/ (Markdown: https://insights.sbomify.com/CVE-2025-65117/index.md)
```

## Sources

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

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