CVE-2025-10918
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 default permissions in the agent of Ivanti Endpoint Manager before version 2024 SU4 allows a local authenticated attacker to write arbitrary files anywhere on disk
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 agent before version 2024 SU4 ships with insecure default file system permissions that allow any locally authenticated user to write arbitrary files to any location on disk. This can be exploited to escalate privileges to SYSTEM or achieve code execution.
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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Locate Ivanti Endpoint Manager agent installationCheck common installation paths such as C:\Program Files\Ivanti\EndpointManager\, or search for 'Endpoint Manager' in Add/Remove Programs. Look for the core ServiceHost.exe or similar core agent executables.Affected if The agent is installed but version is below 2024 SU4, or version cannot be determined and falls within the < 2024 SU4 range.
-
Determine installed agent versionRight-click the core executable (such as ServiceHost.exe) in the installation directory, select Properties, and check the File Version on the Details tab. Alternatively, run 'wmic product get name,version' or check the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for Ivanti Endpoint Manager.Affected if The displayed version is any release prior to 2024 SU4, or shows '2024' without SU4 (SU1, SU2, SU3, or no_SU), indicating it is in the vulnerable < 2024 SU4 range.
-
Verify agent service exists and runs as SYSTEMOpen Services console (services.msc), locate the Ivanti Endpoint Manager service (often named 'Endpoint Manager' or 'Core', depending on version), right-click and select Properties. Check the 'Log On' account - it is typically set to run as SYSTEM or a domain admin account.Affected if The service runs with elevated privileges (SYSTEM or similar), which combined with the insecure file permissions allows a low-privileged user to modify service binaries and escalate to SYSTEM.
-
Inspect file system permissions on installation directoryRight-click the Ivanti Endpoint Manager installation folder (e.g., C:\Program Files\Ivanti\EndpointManager\), select Properties, go to the Security tab, and examine permissions for the 'Users' group or 'Authenticated Users'. Verify if these groups have Write or Modify permissions to the root installation folder or critical subfolders like Agent or Core.Affected if Authenticated Users or the Users group has Write or Full Control permissions to the agent installation directory, allowing any local user to overwrite executable files.
-
Check for weak permissions on executable subfoldersNavigate to subfolders within the installation directory, such as \Agent\ or \Core\, and inspect their permissions. Use 'icacls' command (e.g., icacls 'C:\Program Files\Ivanti\EndpointManager\Agent') to list permissions explicitly for standard user accounts.Affected if Standard user accounts can write to folders containing executable files (.exe, .dll) or configuration files, which enables arbitrary code execution by replacing legitimate binaries.
Your environment is affected if the Ivanti Endpoint Manager agent is installed with a version prior to 2024 SU4 and standard Windows users have Write or Modify permissions to the installation directory or its executable subfolders.
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
Apply Ivanti Endpoint Manager 2024 SU4 or later to remediate the insecure default permissions in the agent.
2024 SU4 (or later)
- Verify current Ivanti Endpoint Manager version by checking the agent or console
- Download Ivanti Endpoint Manager version 2024 SU4 or later from the Ivanti portal or authorized distribution channel
- Review Ivanti upgrade documentation for prerequisites and backup procedures
- Create a backup of the current configuration and database
- Test the upgrade in a non-production environment first
- Apply the upgrade to the production environment following Ivanti's documented upgrade procedure
- Verify the upgrade was successful and agent connectivity is restored
- Confirm the file permission vulnerability is remediated by checking that the agent files have restricted permissions
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-2025-10918 — 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-10918 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