CVE-2024-22026
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 · uneditedA local privilege escalation vulnerability in EPMM before 12.1.0.0 allows an authenticated local user to bypass shell restriction and execute arbitrary commands on the appliance.
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 confidenceA local privilege escalation vulnerability in EPMM versions before 12.1.0.0 allows an authenticated local user to bypass built-in shell restrictions and execute arbitrary commands on the appliance, potentially achieving elevated 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< 12.1.0.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 EPMM is installed on the systemLocate the Ivanti Endpoint Manager Mobile installation through system services, running processes, or common installation directories. Check for the EPMM service or associated processes.Affected if EPMM is not found on the system, the user is not affected by this specific vulnerability.
-
Identify the installed EPMM versionUse the product's built-in version reporting mechanism or check the version information in the installation directory. This is typically accessible through the EPMM admin interface, service information, or version file within the installation.Affected if Unable to determine the version - further investigation needed.
-
Compare installed version against 12.1.0.0Take the identified version number and compare it numerically against 12.1.0.0. Any version prior to 12.1.0.0 (including 12.0.x, 11.x, 10.x, and earlier) falls within the vulnerable range.Affected if The installed version is lower than 12.1.0.0 - the system is affected by this vulnerability.
-
Verify local user authentication contextDetermine if there are any locally authenticated users on the system. This vulnerability requires an authenticated local user to attempt the privilege escalation.Affected if No local users exist or no local user authentication is possible, the exploitation vector is significantly reduced.
The environment is affected if Ivanti Endpoint Manager Mobile is installed with a version number lower than 12.1.0.0 and local user authentication is available.
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 · scoped12.1.0.0
Upgrade EPMM to version 12.1.0.0 or later to remediate this vulnerability.
12.1.0.0
- 1. Identify current EPMM version by checking the appliance management console or running: productversion command
- 2. Review Ivanti Endpoint Manager Mobile 12.1.0.0 release notes for new features, resolved issues, and any configuration changes
- 3. Create a backup of the current EPMM configuration and database
- 4. Schedule a maintenance window for the upgrade
- 5. Download EPMM 12.1.0.0 or later from the Ivanti portal (support.ivanti.com)
- 6. Follow the official upgrade documentation to install version 12.1.0.0
- 7. After upgrade, verify the shell restriction bypass vulnerability is resolved by confirming the fix is applied
- 8. Validate that core EPMM functions (device enrollment, policies, profiles) are working correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22026 — 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-2024-22026 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