dbcve.org
VantageApplication · Lenovo

CVE-2026-1717

MEDIUM · 5.5 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 1.0.0.138 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
An input validation vulnerability was reported in the LenovoProductivitySystemAddin used in Lenovo Vantage and Lenovo Baiying that could allow a local authenticated user to terminate arbitrary processes with elevated 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 confidence

A local authenticated user can exploit an input validation flaw in LenovoProductivitySystemAddin (used by Lenovo Vantage and Lenovo Baiying) to terminate arbitrary processes with elevated privileges. The vulnerability stems from insufficient validation of process identifiers or references passed to the process termination functionality.

MitigationApply vendor-supplied patches for Lenovo Vantage and Lenovo Baiying when available. Until patches are released, restrict local user privileges where feasible and monitor for suspicious process termination activity.

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
VantageApplication
Affected:< 1.0.0.138

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. Check if Lenovo Vantage is installed
    Open Windows Settings > Apps > Apps & features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed software and versions
    Affected if Lenovo Vantage is found with a version lower than 1.0.0.138
  2. Check for LenovoProductivitySystemAddin component
    Look for the DLL or add-in component named LenovoProductivitySystemAddin in the Lenovo Vantage installation directory (typically C:\Program Files\Lenovo\Lenovo Vantage\ or C:\Program Files (x86)\Lenovo\Lenovo Vantage\)
    Affected if The LenovoProductivitySystemAddin component exists in the installation directory
  3. Check if Lenovo Baiying is installed
    Search for Lenovo Baiying in Windows installed programs (Settings > Apps > Apps & features) or check for its installation directory under C:\Program Files\Lenovo\ or C:\Program Files (x86)\Lenovo\
    Affected if Lenovo Baiying is installed and contains the LenovoProductivitySystemAddin component
  4. Verify process termination functionality exposure
    Examine the LenovoProductivitySystemAddin component permissions and configuration files in the installation directory for any process termination-related modules or APIs accessible to local users
    Affected if The process termination functionality in LenovoProductivitySystemAddin is exposed to authenticated local users without proper validation

You are affected if Lenovo Vantage version is below 1.0.0.138 or if Lenovo Baiying with the LenovoProductivitySystemAddin component is installed, as either allows a local authenticated user to terminate arbitrary processes with elevated privileges.

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 1.0.0.138 or later
Fixed in 1.0.0.138
Interim mitigation

Apply vendor-supplied patches for Lenovo Vantage and Lenovo Baiying when available. Until patches are released, restrict local user privileges where feasible and monitor for suspicious process termination activity.

Recommended fix High confidence

Lenovo Vantage version 1.0.0.138 or later

  1. Identify the current version of Lenovo Vantage installed on the system
  2. Navigate to the official Lenovo support website (support.lenovo.com) or use the built-in update feature within Lenovo Vantage
  3. Check for updates and ensure the version is updated to 1.0.0.138 or later
  4. Verify the update was successful by checking the version number in the application settings or 'About' section
  5. Restart the system if required to complete the installation of the update

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

Fix this in Vantage Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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