dbcve.org
Windows Server 2012Operating system · Microsoft

CVE-2025-27480

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
Use after free 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 use-after-free vulnerability exists in the Remote Desktop Gateway Service that allows an unauthenticated remote attacker to achieve code execution. The vulnerability stems from improper memory management where memory is accessed after being freed, leading to potential arbitrary code execution in the context of the service.

MitigationApply the relevant Microsoft security patch for CVE-2025-27480 to all affected Windows systems running Remote Desktop Gateway. Until patches are applied, restrict network access to RDP Gateway ports (default 443) to trusted sources only.

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 2012Operating system
Affected:all versions= r2
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. Verify Remote Desktop Gateway service presence
    Open Services console (services.msc) or run 'Get-Service -Name TermService' and check if the Remote Desktop Gateway service ( TERMSERVICE) is installed and running. Also check for the 'Remote Desktop Gateway' role via Server Manager or 'Get-WindowsFeature RDS-Gateway'.
    Affected if The Remote Desktop Gateway service or role is installed/enabled on the system.
  2. Check Windows Server version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' or query the registry at HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion to obtain the full build number.
    Affected if The installed version falls outside the fixed builds: Server 2012 (any version), Server 2016 < 10.0.14393.7969, Server 2019 < 10.0.17763.7136, Server 2022 < 10.0.20348.3453, Server 2022 23h2 < 10.0.25398.1551, or Server 2025 < 10.0.26100.3775.
  3. Confirm RD Gateway listener is active
    Run 'netsh routing ip http show interface' or check registry at HKLM\SYSTEM\CurrentControlSet\Services\TermService\Parameters\ServiceDll to verify the Terminal Services (TermService) DLL is loaded. Use 'netstat -ano | findstr :443' to check if port 443 (default RD Gateway port) is listening.
    Affected if The RD Gateway service is listening on network ports, exposing the vulnerability to remote attackers.

The system is affected if it runs any of the unpatched Windows Server versions listed AND has Remote Desktop Gateway service or role enabled and exposed on the network.

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 the relevant Microsoft security patch for CVE-2025-27480 to all affected Windows systems running Remote Desktop Gateway. Until patches are applied, restrict network access to RDP Gateway ports (default 443) to trusted sources only.

Recommended fix High confidence

Windows Server 2016 to build 10.0.14393.7969 | Windows Server 2019 to build 10.0.17763.7136 | Windows Server 2022 to build 10.0.20348.3453 | Windows Server 2022 23h2 to build 10.0.25398.1551 | Windows Server 2025 to build 10.0.26100.3775 | Windows Server 2012/2012 R2 to a supported version such as W

  1. Identify the current Windows Server build version by running 'winver' or 'systeminfo' in Command Prompt
  2. For Windows Server 2016: Apply the March 2025 or later Windows Update to reach build 10.0.14393.7969
  3. For Windows Server 2019: Apply the March 2025 or later Windows Update to reach build 10.0.17763.7136
  4. For Windows Server 2022: Apply the March 2025 or later Windows Update to reach build 10.0.20348.3453
  5. For Windows Server 2022 23h2: Apply the March 2025 or later Windows Update to reach build 10.0.25398.1551
  6. For Windows Server 2025: Apply the March 2025 or later Windows Update to reach build 10.0.26100.3775
  7. For Windows Server 2012/2012 R2: Upgrade to a supported Windows Server version as these releases are end-of-life with no security updates
  8. Verify the update was applied by checking the build number in Windows Update history
Caveat Windows Server 2012/2012 R2 have reached end of support and receive no further security patches; upgrade to a supported version required; standard Windows Update best practices apply

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

Fix this in Windows Server 2012 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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