CVE-2025-11622
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 · uneditedInsecure deserialization in Ivanti Endpoint Manager before version 2024 SU4 allows a local authenticated attacker to escalate their privileges.
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 confidenceIvanti Endpoint Manager versions prior to 2024 SU4 contain an insecure deserialization vulnerability that allows a local authenticated user to deserialize untrusted data, leading to privilege escalation from their existing account to higher system privileges.
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< 2024= 2024CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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.
-
Confirm Ivanti Endpoint Manager is installedCheck for Ivanti Endpoint Manager installation directory (commonly C:\Program Files\Ivanti\EndpointManager or similar) or look for the 'Ivanti Endpoint Manager' service in Windows ServicesAffected if The software is installed on the system
-
Identify the installed versionCheck the version of Ivanti Endpoint Manager by examining the executable or DLL properties (typically CoreServer.exe or a version file in the installation directory), or use the product's built-in About/Version information in the consoleAffected if The version cannot be determined or is lower than 2024 SU4
-
Compare version against affected rangesCompare your installed version number to the affected ranges: versions prior to 2024 (such as 2023, 2022, etc.) and version 2024 (base release). Versions 2024 SU4 and later are NOT affectedAffected if The installed version is less than 2024, or the installed version is exactly 2024 (any build before SU4)
-
Verify the service is runningConfirm the Ivanti Endpoint Manager Core Server service is currently running (check in Windows Services or via command: sc query 'Ivanti Endpoint Manager')Affected if The service is active and the version is within the affected range
You are affected if Ivanti Endpoint Manager is installed with a version prior to 2024 SU4 (including version 2024 base release) and the service is running.
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 · scoped2024
Upgrade Ivanti Endpoint Manager to version 2024 SU4 or later to remediate the insecure deserialization vulnerability.
2024 SU4 (Endpoint Manager 2024 Service Update 4)
- 1. Back up the Ivanti Endpoint Manager database and configuration according to vendor documentation
- 2. Download Ivanti Endpoint Manager version 2024 SU4 from the official Ivanti download portal or support site
- 3. Review the upgrade guide in the Ivanti Endpoint Manager 2024 SU4 release notes for any prerequisite steps
- 4. Apply the upgrade to the Endpoint Manager server following the standard upgrade procedure
- 5. Verify the upgrade was successful by checking the version number in the product console
- 6. Test that normal Endpoint Manager functionality is working as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11622 — 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-2025-11622 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