dbcve.org
Windows Server 2016Operating system · Microsoft

CVE-2025-27482

HIGH · 8.1 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 10.0.14393.7969 / 10.0.17763.7136 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Sensitive data storage in improperly locked memory in Remote Desktop Gateway Service allows an unauthorized attacker to execute code 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

A vulnerability in Remote Desktop Gateway Service allows sensitive data to be stored in improperly locked memory, potentially enabling an unauthenticated remote attacker to execute arbitrary code by exploiting the memory handling weakness.

MitigationApply Microsoft security updates for this vulnerability and ensure Remote Desktop Gateway services are not directly exposed to untrusted networks.

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 Server 2016Operating system
Affected:< 10.0.14393.7969
Windows Server 2019Operating system
Affected:< 10.0.17763.7136
Windows Server 2022Operating system
Affected:< 10.0.20348.3453
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1551
Windows Server 2025Operating system
Affected:< 10.0.26100.3775

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

CVSS:3.1/AV:N/AC:H/PR:N/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. Identify Windows Server version
    Run 'winver' or 'systeminfo | findstr Build' to obtain the exact OS build number
    Affected if The build number is below the threshold for your specific Windows Server version (2016: 14393.7969, 2019: 17763.7136, 2022: 20348.3453, 2022 23h2: 25398.1551, 2025: 26100.3775)
  2. Confirm Windows Server edition
    Run 'winver' or check System Properties to identify whether you are running Standard, Datacenter, or 23H2 edition, as thresholds differ between editions
    Affected if You are running an affected edition with a build number below its specific threshold
  3. Check if Remote Desktop Gateway service exists
    Run 'Get-Service -Name UmRdpService' in PowerShell or open Services (services.msc) and look for Remote Desktop Gateway
    Affected if The UmRdpService is present on the system indicating Remote Desktop Gateway component is installed

Your environment is affected if you are running a Windows Server version within the affected build ranges AND the Remote Desktop Gateway service or role is installed on the system.

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.14393.7969 / 10.0.17763.7136 / 10.0.20348.3453 or later
Fixed in 10.0.14393.796910.0.17763.713610.0.20348.3453
Interim mitigation

Apply Microsoft security updates for this vulnerability and ensure Remote Desktop Gateway services are not directly exposed to untrusted networks.

Recommended fix High confidence

Windows Server 2016 to build 10.0.14393.7969 or later | Windows Server 2019 to build 10.0.17763.7136 or later | Windows Server 2022 to build 10.0.20348.3453 or later | Windows Server 2022 23h2 to build 10.0.25398.1551 or later | Windows Server 2025 to build 10.0.26100.3775 or later

  1. Identify the current Windows Server version and build number by running 'winver' or 'systeminfo' command
  2. Locate the appropriate Microsoft Security Update for your Windows Server version from catalog.update.microsoft.com or via Windows Update
  3. Apply the security update that corresponds to your Windows Server version's fixed build (2016: 10.0.14393.7969, 2019: 10.0.17763.7136, 2022: 10.0.20348.3453, 2022 23h2: 10.0.25398.1551, 2025: 10.0.26100.3775)
  4. Restart the server as required by the security update
  5. Verify the installed build matches or exceeds the fixed version using 'winver'
Caveat Standard Windows Server update risks apply - ensure backups and test in staging before production deployment

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

Fix this in Windows Server 2016 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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