CVE-2026-22619
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedEaton Intelligent Power Protector (IPP) is affected by insecure library loading in its executable, which could lead to arbitrary code execution by an attacker with access to the software package. This security issue has been fixed in the latest version of Eaton IPP software which is available on the Eaton download center.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceEaton Intelligent Power Protector (IPP) contains an insecure library loading vulnerability where the application loads executable libraries without secure path specification. An attacker with access to the software package can place a malicious library file in a location where the application will load it, achieving arbitrary code execution with the privileges of the running application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.00CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify if Eaton Intelligent Power Protector is installedCheck common installation directories for the IPP executable (typically in C:\Program Files\Eaton\Intelligent Power Protector or C:\Program Files (x86)\Eaton\Intelligent Power Protector). Also check Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Eaton\Intelligent Power Protector or HKEY_CURRENT_USER\SOFTWARE\Eaton\Intelligent Power Protector.Affected if The application is present on the system
-
Determine installed version of Eaton IPPLocate the main executable (PowerManager.exe or similar) in the installation folder, right-click and view Properties, or use command: wmic product where "name like '%Intelligent Power Protector%'" get versionAffected if Version returned is less than 2.00 or cannot be determined (null/empty)
-
Check if the application service or process runs with elevated privilegesOpen Services control panel, locate the Eaton Intelligent Power Protector service, check the Log On account. Also observe if the service runs as LocalSystem, a domain account, or a specific service account.Affected if The service runs with elevated privileges (LocalSystem, administrator account, or domain admin)
-
Inspect library loading behaviorUse a tool like Process Monitor (from Sysinternals) to observe DLL loading when the application starts. Look for libraries loaded from non-secure paths (current directory, temp folders, or application directory without full path specification).Affected if The application loads DLLs without fully qualified paths, allowing potential DLL hijacking
System is affected if Eaton Intelligent Power Protector is installed with a version below 2.00 and the application is in use, as insecure library loading can be exploited to execute arbitrary code.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.00
Update Eaton Intelligent Power Protector to the latest version available from the official Eaton download center to remediate this vulnerability.
Version 2.00 or later (latest version available from Eaton)
- 1. Navigate to the official Eaton download center to obtain the latest version of Eaton Intelligent Power Protector
- 2. Uninstall the current version of Intelligent Power Protector from the affected system
- 3. Download and install the latest version (version 2.00 or later) of Eaton Intelligent Power Protector
- 4. Verify the installed version matches the patched release
- 5. Restart any services or systems running Intelligent Power Protector to ensure the patched version is active
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22619 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22619 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data