Which PowerShell builds fix it?
| Affected product | Microsoft fixed build | Remediation |
|---|---|---|
| PowerShell 7.6 | 7.6.10 | For PowerShell 7.6, update to fixed build 7.6.10 or later. |
| PowerShell 7.7 | 7.7.0 | For PowerShell 7.7, update to fixed build 7.7.0 or later. |
For administrators, the practical check is to verify the build that scheduled jobs and automation actually run, not just the build that opens in an interactive shell. If you manage both branches, track them separately and compare each installation against its own fixed build. An updated administrator workstation does not establish that a separate automation runner is patched.
Why Microsoft rates exploitation as less likely
Microsoft assigns a CVSS base score of 6.1, a temporal score of 5.3, and the weakness identifier CWE-522. The full vector is CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N/E:U/RL:O/RC:C.
The advisory explains that high attack complexity (AC:H) means specific conditions, such as particular protocol settings or configurations, must be in place for an attack to succeed. That makes widespread or opportunistic exploitation less likely. The vector also records required user interaction and high confidentiality impact, with no direct integrity or availability impact scored. In other words, the conditions limit the opportunity for an attack, but credentials can still be exposed if it succeeds.
- Publicly disclosed: No
- Exploited: No
- Microsoft exploitation assessment: Exploitation Less Likely
- Customer action required: Yes
References
- Official MSRC or vendor evidence api.msrc.microsoft.com
- Official MSRC or vendor evidence msrc.microsoft.com
- Official MSRC or vendor evidence api.msrc.microsoft.com