How severe is GHSA-q7x5-x7rr-2859?

GHSA-q7x5-x7rr-2859 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-q7x5-x7rr-2859?

GHSA-q7x5-x7rr-2859 affects the following packages: Microsoft.PowerShell.SDK (NuGet), Microsoft.PowerShell.SDK (NuGet), Microsoft.PowerShell.SDK (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-q7x5-x7rr-2859?

Update Microsoft.PowerShell.SDK to 7.0.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q7x5-x7rr-2859 is resolved across your whole dependency graph.

How do I detect GHSA-q7x5-x7rr-2859 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.PowerShell.SDK, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-q7x5-x7rr-2859 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-q7x5-x7rr-2859 actively exploited in the wild?

No public exploit code has been indexed for GHSA-q7x5-x7rr-2859 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-q7x5-x7rr-2859?

GHSA-q7x5-x7rr-2859 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 49th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-q7x5-x7rr-2859 published, and has it been updated?

GHSA-q7x5-x7rr-2859 was published on April 16, 2022 and was last updated on October 13, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET

.NET NuGet

Not in CISA KEV

HIGH severity

GHSA-q7x5-x7rr-2859 — Microsoft.PowerShell.SDK

HIGH

GHSA-q7x5-x7rr-2859 is a high-severity (CVSS 7.8) vulnerability in Microsoft.PowerShell.SDK. A fix is available for Microsoft.PowerShell.SDK — see the affected versions and patch details below.

PowerShell Elevation of Privilege Vulnerability

Also known asBIT-powershell-2022-26788CVE-2022-26788

Published

Apr 16, 2022

Updated

Oct 13, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Sep 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs49th percentile — riskier than 49% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-q7x5-x7rr-2859 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected

.NETMicrosoft.PowerShell.SDK.NETMicrosoft.PowerShell.SDK.NETMicrosoft.PowerShell.SDK

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

PowerShell Elevation of Privilege Vulnerability.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Microsoft.PowerShell.SDK`	≥ 7.0.0-preview.1&&< 7.0.10	7.0.10`dotnet add package Microsoft.PowerShell.SDK --version 7.0.10`
.NETNuGet	`Microsoft.PowerShell.SDK`	≥ 7.1.0-preview.1&&< 7.1.7	7.1.7`dotnet add package Microsoft.PowerShell.SDK --version 7.1.7`
.NETNuGet	`Microsoft.PowerShell.SDK`	≥ 7.2.0-preview.1&&< 7.2.3	7.2.3`dotnet add package Microsoft.PowerShell.SDK --version 7.2.3`

Affected Products

10 products · 21 configurations

Application

powershellmicrosoft

≥ 7.2 && < 7.2.3

range

windows 8.1microsoft

all

windows 10microsoft

6 versions

20h221h121h2160718091909

windows 11microsoft

all

windows rt 8.1microsoft

all

windows server 2008microsoft

1 version

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.PowerShell.SDK, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Microsoft.PowerShell.SDK to 7.0.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q7x5-x7rr-2859 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

PowerShell Elevation of Privilege Vulnerability.

O3 Security · Impact-Aware SCA

Is GHSA-q7x5-x7rr-2859 in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works