CVE Intelligence
Skip to main content
HIGH

CVE-2025-59887

CVE-2025-59887 Vulnerability Analysis & Exploit Intelligence

Improper authentication of library files in the Eaton UPS Companion software installer could lead to arbitrary code execution of an attacker with the access to the software package. This security issue has been fixed in the latest version of EUC which is available on the Eaton download center.

Published Updated Sources: cvelistV5, Eaton

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

chance of exploitation in 30 days

Affects

eaton

eaton_ups_companion_software

CVSS base

8.6

HIGH

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

eaton

Products (1)

eaton ups companion software

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
8.6CVSS 3.1HIGH——cvelistV5

Weakness & attack patterns

  • CWE-427

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable
  • T1574.009Hijack Execution Flow: Path Interception by Unquoted Path
  • T1574.001Hijack Execution Flow: DLL search order hijacking

References

1 on the record

Elsewhere on this site

  • eatonevery CVE for this vendor
  • CWE-427other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.