CVE-2019-6198 is a local privilege escalation in Lenovo PC Manager before version 2.8.90.11211, scored 7.8 High. The weakness is improper authentication. Update PC Manager to 2.8.90.11211 or later. The record gives no further technical detail, so confirm specifics against the Lenovo advisory.
What's affected
- Product: Lenovo PC Manager.
- Affected: versions before 2.8.90.11211, per the NVD record.
- Fixed: 2.8.90.11211 is the first version outside the affected range in the record. The Lenovo advisory page is a script driven page that did not render for this post, so confirm the fix version there.
- Severity: 7.8 High (AV:L/AC:L/PR:L/UI:N).
- Weakness: improper authentication. The record gives no technical detail beyond that.
How to check if you're exposed
- Open the PC Manager application on a machine and read its version in the about or settings screen. Anything below 2.8.90.11211 is in range.
- In a managed fleet, use your software inventory tool to filter on the product name and version.
- If PC Manager updates itself through its own channel, open the application and look for its version and update controls.
- Check the Lenovo advisory page referenced by the record for any further affected builds.
What to do now
- Update Lenovo PC Manager to 2.8.90.11211 or later on every machine that has it.
- If the tool is not needed, uninstall it. Vendor utilities are often installed by default and then forgotten.
- Treat the issue as a second stage bug: restrict who can run code on shared machines, since the attacker needs a local account.
- Add vendor utilities to your regular software inventory so version checks do not depend on remembering them.
Why it matters
The record says a local attacker could escalate privileges and tags the cause as improper authentication. It adds no description of the mechanism, and this post does not guess at one. What the record does establish is the shape of the risk: a low privilege local user gaining higher privileges (C:H/I:H/A:H).
Vendor management utilities often run with elevated rights so they can change system settings. That makes authentication inside them a security boundary. The record's KEV flag is false, and the sources available did not describe exploitation.
Quick check
Can someone exploit this over the network?
The record's vector is local, so an attacker needs to be able to run code on the machine first.
Is the fixed version confirmed by Lenovo?
The version comes from the NVD record. The Lenovo page did not render for this post, so check it before you close the ticket.
Sources
- Lenovo advisory referenced by the NVD record: The page needs a script enabled browser and did not render in a plain fetch. Version details come from the NVD record.
Last reviewed: 19 October 2026.