dbcve.org
PowershellApplication · Microsoft

CVE-2025-49734

HIGH · 7.0 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 7.4.12 / 7.5.3 or later.
See remediation →
72/100
Remediation priority · Elevated
Zero-click

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
Improper restriction of communication channel to intended endpoints in Windows PowerShell allows an authorized attacker to elevate privileges locally.

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 · moderate confidence

This is a local privilege escalation vulnerability in Windows PowerShell stemming from improper restriction of communication channels to their intended endpoints. An authorized attacker (already with some local access) can exploit this to elevate privileges. The vulnerability allows PowerShell to communicate with endpoints it shouldn't be able to reach, enabling privilege escalation.

MitigationApply Microsoft security patches for CVE-2025-49734 when released. In the interim, review PowerShell execution policies, restrict PowerShell script execution to least-privilege, and monitor for unusual PowerShell activity indicating privilege escalation attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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.4, < 7.4.12>= 7.5, < 7.5.3
Windows 10 1607Operating system
Affected:< 10.0.14393.8422
Windows 10 1809Operating system
Affected:< 10.0.17763.7792
Windows 10 21h2Operating system
Affected:< 10.0.19044.6332
Windows 10 22h2Operating system
Affected:< 10.0.19045.6332
Windows 11 22h2Operating system
Affected:< 10.0.22621.5909
Windows 11 23h2Operating system
Affected:< 10.0.22631.5909
Windows 11 24h2Operating system
Affected:< 10.0.26100.6508

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
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check PowerShell version
    Run '$PSVersionTable.PSVersion' in PowerShell to get the major, minor, and patch numbers
    Affected if Version is 7.4.x where x is less than 12, or version is 7.5.x where x is less than 3
  2. Check Windows 10 build version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to get the Windows 10 build number
    Affected if Running Windows 10 version 1607 with build < 14393.8422, version 1809 with build < 17763.7792, version 21h2 with build < 19044.6332, or version 22h2 with build < 19045.6332
  3. Check Windows 11 build version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to get the Windows 11 build number
    Affected if Running Windows 11 version 22h2 with build < 22621.5909, version 23h2 with build < 22631.5909, or version 24h2 with build < 26100.6508
  4. Review PowerShell logs for unauthorized endpoint communication
    Check Windows Event Viewer under Application and Services Logs > Windows PowerShell for unusual outbound connection attempts or script activity from low-privilege users attempting to access protected endpoints
    Affected if Logs show PowerShell scripts or commands attempting to communicate with endpoints outside expected boundaries from user contexts that should not have such access

You are affected if your PowerShell version is 7.4.x before 7.4.12 or 7.5.x before 7.5.3, or your Windows version/build falls below any of the thresholds listed in the affected products.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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
Upgrade available Upgrade to 7.4.12 / 7.5.3 / 10.0.14393.8422 or later
Fixed in 7.4.127.5.310.0.14393.8422
Interim mitigation

Apply Microsoft security patches for CVE-2025-49734 when released. In the interim, review PowerShell execution policies, restrict PowerShell script execution to least-privilege, and monitor for unusual PowerShell activity indicating privilege escalation attempts.

Recommended fix High confidence

PowerShell 7.4.12 or 7.5.3 (Windows version-specific security updates to reach fixed builds)

  1. Identify current PowerShell version by running: $PSVersionTable.PSVersion
  2. For PowerShell 7.x installations: Upgrade to version 7.4.12 or 7.5.3 using: winget install Microsoft.PowerShell --version 7.4.12 (or 7.5.3)
  3. Alternatively, use: Install-Module -Name PowerShell -RequiredVersion 7.4.12 -Force -AllowClobber
  4. For Windows built-in PowerShell (Windows PowerShell 5.1): Apply Windows security updates via Windows Update to reach the fixed OS builds (10.0.14393.8422, 10.0.17763.7792, 10.0.19044.6332, 10.0.19045.6332, 10.0.22621.5909, 10.0.22631.5909, or 10.0.26100.6508 depending on Windows version)
  5. Verify fix by confirming PowerShell version is 7.4.12+ or 7.5.3+
Caveat PowerShell 7.x upgrades are generally backward compatible but verify scripts against the target version before production deployment

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

Fix this in Powershell Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49734 — 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-2025-49734 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