dbcve.org
Windows 11 22h2Operating system · Microsoft

CVE-2025-33054

HIGH · 8.1 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.22621.5624 / 10.0.22631.5624 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

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
Insufficient UI warning of dangerous operations in Remote Desktop Client allows an unauthorized attacker to perform spoofing over a network.

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

The Remote Desktop Client has insufficient user interface warnings when users initiate dangerous operations, allowing an unauthorized attacker on the network to perform spoofing attacks. The client fails to adequately alert users about risky connection behaviors that could enable an attacker to impersonate the RDP server.

MitigationImplement clear, contextual UI warnings in the Remote Desktop Client for operations that could enable spoofing, such as connecting to servers with untrusted certificates or redirecting credentials. User education on heeding these warnings is also recommended.

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
Windows 11 22h2Operating system
Affected:< 10.0.22621.5624
Windows 11 23h2Operating system
Affected:< 10.0.22631.5624
Windows 11 24h2Operating system
Affected:< 10.0.26100.4652
Windows Server 2025Operating system
Affected:< 10.0.26100.4652

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

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

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. Locate the Remote Desktop Client executable
    Open File Explorer and navigate to C:\Windows\System32\mstsc.exe, or run "Get-Item C:\Windows\System32\mstsc.exe" in PowerShell
    Affected if The file exists on the system (RDP client is installed)
  2. Retrieve the mstsc.exe file version
    Right-click mstsc.exe, select Properties, go to the Details tab, and note the File version field; or run "(Get-Item C:\Windows\System32\mstsc.exe).VersionInfo.FileVersion" in PowerShell
    Affected if The file version is lower than the fixed versions for your Windows build
  3. Identify the installed Windows version and build
    Run "winver" from the Run dialog, or run "Get-ComputerInfo | Select-Object OsName, OsVersion, OsBuildNumber" in PowerShell
    Affected if The system is Windows 11 22h2, 23h2, 24h2, or Windows Server 2025
  4. Compare against affected version ranges
    Cross-reference the mstsc.exe version with the affected ranges: for Windows 11 22h2 check if < 10.0.22621.5624; for 23h2 check if < 10.0.22631.5624; for 24h2 or Server 2025 check if < 10.0.26100.4652
    Affected if The installed mstsc.exe version falls below the threshold for your specific Windows version

A system is affected if it runs Windows 11 22h2, 23h2, 24h2, or Windows Server 2025 and the Remote Desktop Client (mstsc.exe) version is lower than 10.0.22621.5624, 10.0.22631.5624, or 10.0.26100.4652 respectively.

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 10.0.22621.5624 / 10.0.22631.5624 / 10.0.26100.4652 or later
Fixed in 10.0.22621.562410.0.22631.562410.0.26100.4652
Interim mitigation

Implement clear, contextual UI warnings in the Remote Desktop Client for operations that could enable spoofing, such as connecting to servers with untrusted certificates or redirecting credentials. User education on heeding these warnings is also recommended.

Recommended fix High confidence

Windows 11 22h2 build 10.0.22621.5624 | Windows 11 23h2 build 10.0.22631.5624 | Windows 11 24h2 build 10.0.26100.4652 | Windows Server 2025 build 10.0.26100.4652

  1. Open Settings on the Windows system
  2. Navigate to Windows Update (Settings > Windows Update)
  3. Click 'Check for updates' to scan for available updates
  4. Install all available updates, particularly any security updates for the Remote Desktop Client
  5. Restart the system if prompted
  6. Verify the installed version matches or exceeds the fixed build: Windows 11 22h2 should be 10.0.22621.5624 or later, Windows 11 23h2 should be 10.0.22631.5624 or later, Windows 11 24h2 and Windows Server 2025 should be 10.0.26100.4652 or later
Caveat Standard Windows update applies; no known breaking changes for this security patch

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

Fix this in Windows 11 22h2 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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