dbcve.org
Care CenterApplication · Acer

CVE-2026-9490

MEDIUM · 5.5 CVSS v3.1 Published 2026-05-25
Fix available
A fix is available. Upgrade to 4.00.3060 or later.
See remediation →
57/100
Remediation priority · Elevated
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 security vulnerability has been identified in Acer Care Center where the ACCSvc service creates a Named Pipe with a weak Security Descriptor. This vulnerability allows an authenticated local user to connect and send a specially crafted message (message type 0x03) to the pipe, causing the service to crash with exit code 1067 (ERROR_PROCESS_ABORTED). To mitigate this potential local service disruption, Acer requires users to update the software to the latest version.

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 Care Center's ACCSvc service creates a Windows Named Pipe with an insecure Security Descriptor (weak ACL), allowing any authenticated local user to connect. An attacker with local access can send a specially crafted message (type 0x03) to the pipe, triggering a service crash (exit code 1067/ERROR_PROCESS_ABORTED), resulting in local denial of service.

MitigationUpdate Acer Care Center to the latest version to obtain the vendor patch that corrects the Named Pipe security descriptor. If the service is not required, consider disabling it to reduce attack surface.

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
Care CenterApplication
Affected:< 4.00.3060

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Verify Acer Care Center installation
    Check for Acer Care Center in installed programs list via Windows Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or inspect Program Files\Acer\Acer Care Center folder
    Affected if Acer Care Center is found on the system
  2. Determine installed version
    Read the version from the executable at Program Files\Acer\Acer Care Center\Acer Care Center.exe, or check the version value in the uninstall registry key
    Affected if Version is less than 4.00.3060 (e.g., 4.00.3000, 3.x.x.x)
  3. Confirm ACCSvc service presence
    Open Services (services.msc) or run 'sc query ACCSvc' via command prompt to check if the ACCSvc service exists
    Affected if ACCSvc service exists on the system
  4. Check ACCSvc service status
    Run 'sc query ACCSvc' and verify the STATE shows RUNNING
    Affected if ACCSvc service is currently running (vulnerability requires the service to be active)
  5. Monitor for crash events
    Check Windows Event Viewer under Windows Logs > Application for recent events from source 'ACCSvc' with exit code 1067 (ERROR_PROCESS_ABORTED)
    Affected if Recent crash events with exit code 1067 tied to ACCSvc are present

User is affected if Acer Care Center version below 4.00.3060 is installed AND the ACCSvc service is present and 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
Upgrade available Upgrade to 4.00.3060 or later
Fixed in 4.00.3060
Interim mitigation

Update Acer Care Center to the latest version to obtain the vendor patch that corrects the Named Pipe security descriptor. If the service is not required, consider disabling it to reduce attack surface.

Recommended fix Moderate confidence

4.00.3060 or later (latest available version)

  1. 1. Navigate to the official Acer support website (support.acer.com) and search for Acer Care Center
  2. 2. Download the latest version of Acer Care Center (version 4.00.3060 or later)
  3. 3. Run the downloaded installer as an administrator
  4. 4. Follow the on-screen installation prompts to complete the update
  5. 5. Restart the computer if prompted by the installer
  6. 6. After installation, verify the version by opening Acer Care Center and navigating to the About or Settings section to confirm version 4.00.3060 or later is installed

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

Fix this in Care Center Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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