CVE-2025-25230
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 · uneditedOmnissa Horizon Client for Windows contains an LPE Vulnerability. A malicious actor with local access where Horizon Client for Windows is installed may be able to elevate 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 · moderate confidenceOmnissa Horizon Client for Windows contains a local privilege escalation (LPE) vulnerability. An attacker with local access to a system where the client is installed may exploit this to gain elevated privileges beyond their current user context.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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.
-
Verify if Omnissa Horizon Client for Windows is installedCheck the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for an entry named 'Omnissa Horizon Client' or 'VMware Horizon Client', or inspect the default installation path C:\Program Files\VMware\Horizon Client\ for the presence of client executables.Affected if The product is not installed on the system.
-
Determine the installed version of Omnissa Horizon ClientRight-click the main Horizon Client executable (usually 'Horizon Client.exe' in the installation directory) and view Properties, or query the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{Installation GUID} for the DisplayVersion value.Affected if The installed version cannot be determined or the client executable is missing.
-
Compare your installed version against the affected version rangeReview the installed version number obtained from the previous step against the vendor's official security advisory for CVE-2025-25230 to identify if your version falls within the vulnerable range.Affected if Your installed version matches a version known to be affected by this CVE.
-
Check if the Horizon Client service or related processes are presentOpen Task Manager or run 'tasklist /FI "IMAGENAME eq Horizon*"' via command prompt to see if Horizon Client-related processes are currently running.Affected if The client is installed and vulnerable, but no Horizon processes are running - the attack surface may be reduced but the system remains vulnerable.
-
Verify user context and client installation scopeCheck whether the client was installed system-wide (requires admin rights) or per-user by examining the installation directory permissions and the original installer account.Affected if The client was installed system-wide and you are running as a standard user - the LPE could allow escalation to administrator privileges.
A system is affected if Omnissa Horizon Client for Windows is installed and the installed version falls within the vulnerable version range specified in the vendor advisory for CVE-2025-25230.
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.
From vendor dataApply the vendor-provided patch or update to Omnissa Horizon Client for Windows as soon as practical. Prioritize patching systems with the client installed in higher-risk environments.
- 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-2025-25230 — 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-25230 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