PowerShell vulnerabilities and fixes

CVEs that mention PowerShell, ranked by priority. 7 tracked.

PowerShell has 7 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 7. Most recent: 2026-10-13. Highest priority: CVE-2026-96251 (score 47/100).

• CVE-2026-96251 HIGH 8.8 UPGRADE Reliance on untrusted inputs in a security decision in Microsoft PowerShell allows an unauthorized attacker to
• CVE-2026-16800 HIGH 8.8 UPGRADE Improper control of generation of code ('Code Injection') in the schedule feature in Devolutions PowerShell Un
• CVE-2026-16801 HIGH 8.8 UPGRADE Improper control of generation of code ('Code Injection') in the variables feature in Devolutions PowerShell U
• CVE-2026-96303 MEDIUM 6.5 UPGRADE Improperly implemented security check for standard in Microsoft PowerShell allows an unauthorized attacker to
• CVE-2026-16798 MEDIUM 6.5 UPGRADE Insertion of sensitive information into sent data in the automation jobs API in Devolutions PowerShell Univers
• CVE-2026-16802 MEDIUM 6.5 UPGRADE Cleartext storage of sensitive information in the variables feature in Devolutions PowerShell Universal 2026.2
• CVE-2026-16799 MEDIUM 5.0 UPGRADE Improper access control in the automation tests and workflows features in Devolutions PowerShell Universal 202

FAQ

How do I fix PowerShell vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is PowerShell being exploited right now?

None of the tracked PowerShell CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which PowerShell CVE should I patch first?

CVE-2026-96251 currently ranks highest (47/100): Reliance on untrusted inputs in a security decision in Microsoft PowerShell allows an unauthorized attacker to.

← Back to latest CVEs