dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-9789

HIGH · 8.5 CVSS v4.0 Published 2026-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/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
A Local Privilege Escalation (LPE) vulnerability affects Acer NitroSense software versions prior to 3.01.3052. The vulnerability stems from the the PSAdminAgent service, which creates a Named Pipe with a weak Access Control List (ACL). This allows any authenticated local user to connect and send commands. Because the service does not check the caller's privileges before running file deletion commands, a low-privileged local user can exploit this to delete arbitrary files with system authority.

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 confidence

Acer NitroSense versions before 3.01.3052 contain a Local Privilege Escalation vulnerability in the PSAdminAgent service. The service creates a Named Pipe with a weak ACL that permits any authenticated local user to connect and send commands. Because the service fails to validate caller privileges before executing file deletion operations, an unprivileged user can delete arbitrary files with SYSTEM authority.

MitigationUpgrade Acer NitroSense to version 3.01.3052 or later. Alternatively, disable the PSAdminAgent service or restrict Named Pipe access until the update can be applied.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Acer NitroSense is installed
    Check for Acer NitroSense installation directory (commonly at C:\Program Files\Acer\NitroSense or C:\Program Files (x86)\Acer\NitroSense). Look for the executable NitroSense.exe and note its version by right-clicking the file, selecting Properties, and checking the Details tab for the Product Version.
    Affected if If NitroSense is installed and the version displayed is lower than 3.01.3052, the system falls within the affected version range.
  2. Verify PSAdminAgent service presence
    Open Services (services.msc) and search for a service named PSAdminAgent, PSAdmin, or similar. Alternatively, open Command Prompt and run: sc queryex type= service state= all | findstr /i "psadmin"
    Affected if If the PSAdminAgent service exists and is installed, the vulnerable component is present on the system.
  3. Confirm service is running
    In Services, check the Status column for PSAdminAgent. If it shows Running, the service is active. Alternatively, run: sc query PSAdminAgent
    Affected if If the PSAdminAgent service exists and is in a Running or Started state, the Named Pipe with weak ACL is active and the vulnerability is exploitable.
  4. Compare installed version to affected range
    Document the exact NitroSense version from step 1. Compare it numerically to 3.01.3052. Any version below 3.01.3052 (such as 3.00.xxxx, 2.x.xxxx, or 1.x.xxxx) is affected.
    Affected if If the installed version is 3.01.3051 or lower, the system is vulnerable to privilege escalation via the PSAdminAgent service.

The environment is affected if Acer NitroSense is installed with a version lower than 3.01.3052 AND the PSAdminAgent service exists and is running on the 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Acer NitroSense to version 3.01.3052 or later. Alternatively, disable the PSAdminAgent service or restrict Named Pipe access until the update can be applied.

Recommended fix High confidence

Acer NitroSense version 3.01.3052

  1. Identify if Acer NitroSense is installed on the system
  2. Check the current version of Acer NitroSense (typically found in Programs and Features or within the application's About/Help section)
  3. If the installed version is prior to 3.01.3052, download Acer NitroSense version 3.01.3052 or later from Acer's official support website (community.acer.com or acer.com)
  4. Install the updated version of Acer NitroSense
  5. Verify the installation was successful by confirming the version is now 3.01.3052 or later

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9789 — 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-9789 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