CVE-2026-58636 pc manager vulnerability
Improper link resolution before file access ('link following') in Window PC Manager allows an authorized attacker to elevate privileges locally.
Quick answer
microsoft pc manager should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Review vendor advisory for affected versions.
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
Improper link resolution before file access ('link following') in Window PC Manager allows an authorized attacker to elevate privileges locally. This affects Microsoft PC Manager and can let a local attacker gain higher privileges. Update or remove PC Manager on affected devices. Keep local user rights limited and review file-system alerts while the update is being deployed.
- Find devices running Microsoft PC Manager that may be affected by CVE-2026-58636.
- Update PC Manager from the official Microsoft channel or remove it if it is not needed.
- Limit local administrator rights on affected devices.
- Review endpoint protection logs for suspicious link, file, or privilege activity.
- Block users from installing unknown system cleaner or management tools.
- Reboot affected devices if the update requires it.
- Isolate a device if privilege abuse is suspected.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm PC Manager is updated or removed on every affected device.
- Run a safe patch compliance check for CVE-2026-58636.
- Review endpoint logs for unusual file link or privilege events after patching.
- Confirm normal device management behavior after the change.
- Save device counts and exception notes.
Trusted references
FAQ
What is affected by CVE-2026-58636?
microsoft pc manager should be checked against the vendor advisory and trusted references linked on this page.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.