Intel

AIKIDO-2026-242730

Microsoft.PowerShell.Commands.Utility is vulnerable to Incorrect Authorization

CVE-2026-96251Published Oct 21, 2026
October 21, 2026

50

CVE Score

Medium

Incorrect Authorization

Are you affected? Scan for Free

TL;DR

The entry point is AddRemoteCommandMetadata in ImplicitRemotingCommands.cs, which builds proxies when Import-PSSession or Export-PSSession imports commands from a PSSession. Before the fix, IsSafeNameOrIdentifier, IsCommandSkippedByServerDeclaration, and IsCommandNameAllowedForImport ran only against commandMetadata.Name, and the method then stored the command under resolvedCommandName. A remote alias could therefore pass those checks under an innocuous name and be stored as the resolved command, including a skip-listed command such as Get-Help or a local command such as PSConsoleHostReadLine, even when -AllowClobber was not set. The console host calls PSConsoleHostReadLine to read the next line and runs the string that proxy returns.

How do I fix this?

Upgrade the Microsoft.PowerShell.Commands.Utility library to the patch version.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and you use Import-PSSession or Export-PSSession to generate implicit remoting proxy modules from a remote session that defines command aliases.

Versions

6.0.4 - 7.4.20

Fixed in 7.4.21

7.5.0 - 7.5.11

Fixed in 7.5.12

7.6.0 - 7.6.6

Fixed in 7.6.7

Background info

Microsoft.PowerShell.Commands.Utility is vulnerable to Incorrect Authorization in versions 6.0.4 - 7.4.20, 7.5.0 - 7.5.11 and 7.6.0 - 7.6.6.

Get secure today,
quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

No credit card required | Scan results in 32 seconds.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea