CVE-2026-6973
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 Input Validation in Ivanti EPMM before versions 12.6.1.1, 12.7.0.1, and 12.8.0.1 allows a remotely authenticated user with administrative access to achieve remote code execution.
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 confidenceImproper input validation in Ivanti EPMM allows a remotely authenticated user with administrative privileges to inject and execute arbitrary code due to insufficient validation of user-supplied input fields.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 runningAccess the EPMM web administration console or check if the EPMM service is listening on its configured portAffected if EPMM is accessible and running on the network
-
Identify EPMM versionLog into the EPMM admin console and navigate to the About or System Information page to view the installed version numberAffected if The displayed version is lower than 12.6.1.1, equal to 12.7.0.0, or equal to 12.8.0.0
-
Verify administrative access controlsReview the EPMM user accounts and confirm whether default administrative credentials have been changed, and check for any unauthorized admin accountsAffected if Administrative credentials are weak, default, or unauthorized accounts exist, as the vulnerability requires admin-level access to exploit
You are affected if EPMM is running and the installed version matches < 12.6.1.1, 12.7.0.0, or 12.8.0.0 while administrative credentials are accessible to an attacker.
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 Ivanti EPMM to version 12.6.1.1, 12.7.0.1, or 12.8.0.1 (or later) to remediate the input validation flaw.
Upgrade to 12.6.1.1, 12.7.0.1, or 12.8.0.1 depending on your current version branch
- 1. Identify your current Ivanti Endpoint Manager Mobile (EPMM) version from the admin console or system settings
- 2. If running a version < 12.6.1.1, upgrade to version 12.6.1.1 or later
- 3. If running version 12.7.0.0, upgrade to version 12.7.0.1 or later
- 4. If running version 12.8.0.0, upgrade to version 12.8.0.1 or later
- 5. After upgrade, verify the new version in the admin console
- 6. Test that administrative functions work correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6973 — 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-6973 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