# CVE-2026-124224: Microsoft Windows PowerShell privilege escalation via symlink following

Source: https://junglewise.ai/threats/cve-2026-124224-improper-link-resolution-before-file-access-link-following-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2026-124224 · Severity: high · CVSS 7 · Published 2026-11-10

Windows PowerShell, a system administration tool used to manage Windows servers and workstations, contains a flaw where it improperly resolves symbolic links before accessing files. An attacker with local access to a system could exploit this to gain elevated privileges, potentially taking complete control of the affected computer.

Technologies: [Microsoft Windows PowerShell](https://junglewise.ai/threats/technologies/windows-powershell). Vendors: [Microsoft](https://junglewise.ai/threats/vendors/microsoft).

## Quick answers

**Is CVE-2026-124224 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-124224 being exploited in the wild.

**How severe is CVE-2026-124224?** High severity, with a CVSS score of 7, published 10 November 2026.

**Which products and versions are affected?** Microsoft Windows PowerShell <UNKNOWN>.

**Is there a fix for CVE-2026-124224?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-124224 attacked?** It is attacked with local access, in an operating system.

**Am I affected by CVE-2026-124224?** Check whether you run Microsoft Windows PowerShell at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is a classic symlink-following issue in Windows PowerShell where file access validation is performed on the symbolic link rather than the target it resolves to. An authenticated local attacker can craft a malicious symbolic link in a predictable location to redirect PowerShell to access sensitive files or execute code with elevated privileges.

## Affected products

- Microsoft Windows PowerShell <UNKNOWN>

## Timeline

- 2026-11-10: disclosed

## References

- [https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-124224](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-124224)

## Related threats

- [Microsoft Windows PowerShell privilege escalation in execution](https://junglewise.ai/threats/cve-2026-124226-execution-with-unnecessary-privileges-in-windows-powershell)
- [Windows PowerShell code injection vulnerability](https://junglewise.ai/threats/cve-2026-124225-improper-control-of-generation-of-code-code-injection-in-windows)
- [Windows PowerShell code injection security feature bypass](https://junglewise.ai/threats/cve-2026-113815-improper-control-of-generation-of-code-code-injection-in-windows)
- [Windows PowerShell untrusted input security decision remote code execution](https://junglewise.ai/threats/cve-2026-85817-reliance-on-untrusted-inputs-in-a-security-decision-in-windows)
- [Microsoft Windows PowerShell security check bypass](https://junglewise.ai/threats/cve-2026-85805-improperly-implemented-security-check-for-standard-in-windows)