dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2026-27788

HIGH · 7.8 CVSS v3.0 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Incorrect permission assignment for critical resource issue exists in ServerView Agents for Windows V11.60.04 and earlier. If this vulnerability is exploited, a local authenticated attacker who can log in to the server where the affected product is installed may obtain SYSTEM privilege.

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 confidence

A local privilege escalation vulnerability exists in ServerView Agents for Windows V11.60.04 and earlier due to incorrect permission assignments on critical resources. An authenticated local attacker who can log into the affected server can exploit these misconfigured permissions to gain SYSTEM-level privileges, achieving full administrative control over the system.

MitigationUpgrade ServerView Agents for Windows to a version newer than V11.60.04. As an interim measure, restrict local access to trusted users only and audit existing administrative accounts.

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.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if ServerView Agents for Windows is installed
    Check for the presence of ServerView Agents installation directories or look for the service in Windows Services (services.msc) with names containing 'ServerView'
    Affected if ServerView Agents for Windows is not installed on the system
  2. Determine the installed version of ServerView Agents
    Locate the ServerView Agents installation directory and check for version information in file properties, README files, or the product's main executable metadata; compare against V11.60.04
    Affected if The installed version is V11.60.04 or earlier (or version cannot be determined but the product is present)
  3. Inspect file and folder permissions on the ServerView installation directory
    Use icacls or a similar tool to review access control lists on the ServerView Agents installation folder and subfolders; look for permissions granted to non-admin users that allow write or modify access to executable locations
    Affected if Low-privileged users have write, modify, or full control permissions on directories containing ServerView executables or DLLs
  4. Check Windows service configuration for ServerView Agents
    Use sc qc or the Services console to examine the service configuration for ServerView-related services; check the binary path and verify if the service runs with elevated privileges (like SYSTEM)
    Affected if Service configuration allows non-admin users to modify executable paths or service parameters
  5. Review permissions on ServerView configuration or data files
    Examine permissions on configuration files, log directories, or data folders used by ServerView Agents; determine if standard users can modify files that are loaded or executed by privileged processes
    Affected if Non-administrative users can modify files that are accessed by ServerView services running with elevated privileges

A system is affected if ServerView Agents for Windows is installed at version V11.60.04 or earlier AND low-privileged users have overly permissive access (write/modify) to service executables, configuration files, or service parameters that can be exploited for privilege escalation to SYSTEM.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade ServerView Agents for Windows to a version newer than V11.60.04. As an interim measure, restrict local access to trusted users only and audit existing administrative accounts.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,820
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,912.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27788 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27788 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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