dbcve.org
PowershellApplication · Microsoft

CVE-2022-41076

HIGH · 8.5 CVSS v3.1 Published 2022-12-13
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
91/100
Remediation priority · Urgent
High EPSS Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
PowerShell Remote Code Execution Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PowershellApplication
Affected:= 7.2= 7.3
Windows 10Operating system
Affected:all versions= 20h2= 21h1= 21h2= 22h2= 1607= 1809
Windows 11Operating system
Affected:all versions
Windows 7Operating system
Affected:all versions
Windows 8.1Operating system
Affected:all versions
Windows Rt 8.1Operating system
Affected:all versions
Windows Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch portal.msrc.microsoft.com →
Recommended fix High confidence

PowerShell 7.2.12+ or 7.3.3+ (depending on your current major version branch)

  1. Identify the currently installed PowerShell version by running '$PSVersionTable.PSVersion' in PowerShell
  2. For PowerShell 7.2.x users: Upgrade to PowerShell 7.2.12 or later by downloading from https://github.com/PowerShell/PowerShell/releases
  3. For PowerShell 7.3.x users: Upgrade to PowerShell 7.3.3 or later by downloading from https://github.com/PowerShell/PowerShell/releases
  4. Alternatively, update via package manager: 'winget install Microsoft.PowerShell --version 7.2.12' or 'winget install Microsoft.PowerShell --version 7.3.3'
  5. Verify the upgrade was successful by running '$PSVersionTable.PSVersion' and confirming the new version is installed
  6. For Windows systems with built-in Windows PowerShell (5.1), ensure Windows Update is applied to receive security patches for CVE-2022-41076
Caveat Review PowerShell 7 release notes for any breaking changes between your current version and the target upgrade version; some cmdlets or module behaviors may have changed

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41076 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41076 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data