🛡️ CVE-2025-65117 — process-optimization

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs administrative privileges on the target. A user must be tricked into taking some action. The scope is changed, meaning a successful attack can affect components beyond the vulnerable one. Rated impact: confidentiality high, integrity high, availability none.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N

• Attack vector: Local — a local account, shell or session on the host is needed.
• Attack complexity: Low — the attack works reliably, with no preparation.
• Privileges required: High — administrative rights are needed first.
• User interaction: Required — someone has to click, open or visit something.
• Scope: Changed — a successful attack reaches components beyond the vulnerable one.
• Confidentiality impact: High — total loss, or loss the attacker controls.
• Integrity impact: High — total loss, or loss the attacker controls.
• Availability impact: None.

Weakness class

CVE-2025-65117 is classified as CWE-676: Use of Potentially Dangerous Function. The product invokes a potentially dangerous function that could introduce a vulnerability if it is used incorrectly, but the function can also be used safely.

Affected software

CVE-2025-65117 is recorded against 1 package.

• process-optimization (fixed in 2025)

Timeline and source

Published on 16 January 2026 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

github.com
softwaresupportsp.aveva.com
www.aveva.com
www.cisa.gov

Other advisories for this package

process-optimization has other advisories on record. If you are patching this one, these are worth checking on the same host:

• CVE-2025-64691 (8.8 High, published 16 Jan 2026)
• CVE-2025-61943 (8.4 High, published 16 Jan 2026)
• CVE-2025-61937 (10.0 Critical, published 16 Jan 2026)
• CVE-2025-65118 (8.8 High, published 16 Jan 2026)
• CVE-2025-64769 (7.1 High, published 16 Jan 2026)
• CVE-2025-64729 (8.1 High, published 16 Jan 2026)

Same weakness in other software

These advisories are the same class of weakness (CWE-676: Use of Potentially Dangerous Function) in other software:

• CVE-2026-14501 (4.3 Medium, published 17 Jul 2026)
• CVE-2025-67604 (5.3 Medium, published 12 May 2026)
• CVE-2024-50307 (5.5 Medium, published 28 Oct 2024)
• CVE-2024-38434 (6.5 Medium, published 21 Jul 2024)
• CVE-2024-37387 (4.0 Medium, published 19 Jun 2024)
• CVE-2022-39063 (7.5 High, published 16 Sep 2022)

Details

Affected Packages

References