CVE-2026-50511
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 · uneditedImproper link resolution before file access ('link following') in Microsoft PC Manager allows an authorized attacker to elevate privileges locally.
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 confidenceA link following vulnerability in Microsoft PC Manager allows a local attacker to manipulate symbolic or hard links to access files or directories they would not normally have permission to access, enabling local privilege escalation.
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< 3.21.6.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Find installed Microsoft PC Manager versionOpen Settings > Apps > Apps & features, locate Microsoft PC Manager, and note the version number shown. Alternatively, open Programs and Features, find Microsoft PC Manager, and check the version column.Affected if The displayed version is lower than 3.21.6.0
-
Verify symlink creation capabilityCheck if the application uses temporary directories where unprivileged users can create symbolic or hard links. Inspect %TEMP%, %LOCALAPPDATA%, or installation subdirectories for write permissions.Affected if Authenticated users can create symlinks/hardlinks in directories used by Microsoft PC Manager for file operations
-
Inspect file operation loggingReview Windows Event Viewer logs or application logs for any file access operations that may involve symlink resolution, particularly around installer or update operations.Affected if Log entries show file operations using relative paths without O_NOFOLLOW validation
You are affected if Microsoft PC Manager version is below 3.21.6.0 and the application performs file operations in directories where unprivileged users can create symbolic or hard links.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.21.6.0
Apply vendor security updates for Microsoft PC Manager when released; in the interim, limit user file system permissions around the application and monitor for suspicious link creation in application directories.
3.21.6.0
- Check the currently installed version of Microsoft PC Manager (e.g., via Help > About or Add/Remove Programs).
- Download the fixed version 3.21.6.0 (or a later version) from the official Microsoft PC Manager download page or the built‑in update mechanism.
- Run the installer and follow the prompts to upgrade the software.
- Restart the application if required and verify that the version is now 3.21.6.0 or higher.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50511 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-50511 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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