CVE-2026-22617
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) uses an insecure cookie configuration, which could allow a network‑based attacker to intercept the cookie and exploit it through a man‑in‑the‑middle attack. This security issue has been fixed in the latest version of Eaton IPP software which is available on the Eaton download centre.
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 · high confidenceEaton Intelligent Power Protector (IPP) has insecure cookie configuration that fails to set security flags (such as Secure, HttpOnly, or SameSite attributes) on session cookies. This allows a network-based attacker positioned between the client and server to intercept cookies via man-in-the-middle attack and hijack user sessions.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
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.
-
Identify if Eaton Intelligent Power Protector is installedCheck for the installation in common locations: C:\Program Files\Eaton\Intelligent Power Protector, or look for the service named 'IPP' in Windows Services (services.msc), or check for Eaton IPP in Add/Remove ProgramsAffected if The application is present and running on the system
-
Determine the installed version of Eaton IPPCheck the version of the installed executable. Common paths: C:\Program Files\Eaton\Intelligent Power Protector\bin\IPP.exe or check the file properties of the main IPP executable. Compare the version number to the affected range (versions before 2.00)Affected if The installed version is less than 2.00
-
Access the IPP web interface to inspect cookiesOpen a web browser and navigate to the Eaton IPP web interface (typically https://localhost or the configured IP address). Open browser Developer Tools (F12), go to the Application tab, and examine cookies under the Application or Storage sectionAffected if The web application is accessible and session cookies are created
-
Verify cookie security flagsIn browser Developer Tools, examine each cookie set by the IPP application. Check if the 'Secure', 'HttpOnly', and 'SameSite' attributes are present in the Set-Cookie headers or visible in the cookie propertiesAffected if Session cookies are missing one or more of the Secure, HttpOnly, or SameSite attributes, indicating the insecure cookie configuration vulnerability is present
A user is affected if Eaton Intelligent Power Protector version less than 2.00 is installed and running, and session cookies created by the web interface lack Secure, HttpOnly, or SameSite security attributes
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 IPP to the latest version available from the Eaton download centre to obtain the vendor patch that fixes the insecure cookie configuration.
Version 2.00 or later (latest available release from Eaton)
- 1. Identify the current version of Eaton Intelligent Power Protector installed in your environment
- 2. Back up all IPP configuration data and any critical settings
- 3. Navigate to the official Eaton download centre to obtain the latest version of Intelligent Power Protector (version 2.00 or later)
- 4. Follow Eaton's documented upgrade procedure to install the new version
- 5. After upgrade, verify that cookies are now transmitted with the 'Secure' attribute by inspecting HTTPS responses
- 6. Test that all IPP functionality works correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22617 — 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-22617 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