CVE-2026-96251 json
Microsoft PowerShell Remote Code Execution Vulnerability
published 2026-10-13 26 d ago modified 2026-10-31 8 d ago also BIT-powershell-2026-96251 , EUVD-2026-100219
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
Reliance on untrusted inputs in a security decision in Microsoft PowerShell allows an unauthorized attacker to execute code over a network.
Patch / fix
- bitnami powershell 7.4.21, 7.5.12, 7.6.7
- Microsoft PowerShell 7.4 7.4.21
- Microsoft PowerShell 7.5 7.5.12
- Microsoft PowerShell 7.6 7.6.8
- powershell Alpine 3.24 7.6.9-r0
alpine advisories ALPINE-CVE-2026-96251
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 26 d ago
Exploit prediction
0.69% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C |
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | powershell | >=7.4.0, <7.4.21 >=7.5.0, <7.5.12 >=7.6.0, <7.6.7 |
7.4.21 7.5.12 7.6.7 |
Affected products
- Microsoft PowerShell 7.4
- Microsoft PowerShell 7.5
- Microsoft PowerShell 7.6
Classification
- Weakness
-
- CWE-807 Reliance on Untrusted Inputs in a Security Decision
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2026-96251
vendor-advisory, patch, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-96251
web
Sources
- CVE List CVE-2026-96251
- NVD CVE-2026-96251
- OSV BIT-powershell-2026-96251
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.