Local code execution via insecure library loading
Published Dec 26, 2025 · Updated Dec 26, 2025
Insecure library loading in Eaton UPS Companion before 3.0 allows local users to execute arbitrary code through the software package. The EUC executable loads a library through an uncontrolled search-path element, although Eaton does not identify the executable or library. Exploitation requires local, low-privileged access to the software package; arbitrary code then runs in the executable's context.
Summary
What happened
Insecure library loading in Eaton UPS Companion before 3.0 allows local users to execute arbitrary code through the software package. The EUC executable loads a library through an uncontrolled search-path element, although Eaton does not identify the executable or library. Exploitation requires local, low-privileged access to the software package; arbitrary code then runs in the executable's context.
The record
- CVE
- CVE-2025-67450
- Published
- Dec 26, 2025
- Updated
- Dec 26, 2025
- Vendor
- Eaton
- Product
- Eaton UPS Companion
- Classifications
- CWE-427, T1574
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 26, 2025CVE publishedPublication date reported by the CVE source.
- Dec 26, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo