CVE-2026-5788
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 · uneditedAn Improper Access Control in Ivanti EPMM before versions 12.6.1.1, 12.7.0.1, and 12.8.0.1 allows a remote unauthenticated attacker to invoke arbitrary methods.
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 EPMM contains an Improper Access Control vulnerability allowing remote unauthenticated attackers to invoke arbitrary methods due to missing authentication checks on certain endpoints. This enables complete system compromise without any credentials.
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.6.1.1= 12.7.0.0= 12.8.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify the installed Ivanti EPMM versionAccess the EPMM admin console and navigate to the System Settings or About page to view the current software version. Alternatively, check the version from the installer package, release notes, or system inventory if managed centrally.Affected if The version matches < 12.6.1.1, = 12.7.0.0, or = 12.8.0.0
-
Confirm the exact version numberVerify the full version string displayed in the admin interface or system information panel. Record the complete version including any build numbers.Affected if The version falls within any of the three vulnerable version ranges specified
-
Determine if the EPMM management interface is network-accessibleTest connectivity to the EPMM web console port (typically 443 or 8443) from an untrusted network segment. Review firewall rules and network ACLs to confirm whether the management URL is exposed to the internet or untrusted internal networks.Affected if The management interface is reachable from networks outside the trusted administrative zone
-
Check for unauthorized access indicatorsReview EPMM audit logs, user activity logs, and administrative event logs for unexpected method invocations, new administrative accounts, or configuration changes made by unknown sources since the deployment date.Affected if Unrecognized administrative actions, new user accounts, or suspicious configuration changes appear in logs without corresponding legitimate admin activity
You are affected if your installed Ivanti EPMM version is less than 12.6.1.1, exactly 12.7.0.0, or exactly 12.8.0.0 AND the management interface is accessible from untrusted networks.
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.6.1.1
Apply vendor patches by upgrading to versions 12.6.1.1, 12.7.0.1, or 12.8.0.1 or later. If immediate patching is not possible, restrict network access to the EPMM management interface using firewall rules or VPN access controls.
12.6.1.1, 12.7.0.1, or 12.8.0.1 (depending on which release train you are on)
- 1. Identify the current installed version of Ivanti Endpoint Manager Mobile (EPMM)
- 2. If running a version < 12.6.1.1, upgrade to version 12.6.1.1
- 3. If running version 12.7.0.0, upgrade to version 12.7.0.1
- 4. If running version 12.8.0.0, upgrade to version 12.8.0.1
- 5. After upgrading, verify the new version is running and confirm the vulnerability is remediated
- 6. Review the Ivanti security advisory at the vendor link for any additional required post-upgrade configuration steps
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5788 — 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-5788 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