# CVE-2025-27480: Windows Remote Desktop Services Remote Code Execution Vulnerability

> An unauthorized attacker can execute code over the network via a use-after-free flaw in the Windows Remote Desktop Gateway Service.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2025
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-79xr-cjjw-p6f2

## What is CVE-2025-27480?

CVE-2025-27480 is a high-severity use after free vulnerability in Microsoft Windows Server 2012, published on 8 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use after free in Remote Desktop Gateway Service allows an unauthorized attacker to execute code over a network.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2025-27480?

It affects 6 products.


Products: Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows Server 2022 23h2, Microsoft Windows Server 2025.

## How do I fix CVE-2025-27480?

No fix has been published for CVE-2025-27480 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-27480 being exploited?

There is no known exploitation of CVE-2025-27480 in the wild and no public exploit code.

Public exploit code:

- Letting attackers run malicious code without needing a cracked password, user interaction, or even a foothold in your network. That’s CVE-2025-27480 (github_poc): https://github.com/mrk336/CVE-2025-27480-The-Silent-Gateway-Risk
- CVE-2025-27480 exposes a buffer overflow in OpenSSH 8.9p1 via a malformed SSH_USERAUTH packet. Attackers can inject shellcode and gain SYSTEM-level access, compromising bastion hosts and downstream CI/CD agents. The article includes sample exploit code and patching guidance (github_poc): https://github.com/mrk336/CVE-2025-27480

## Other vulnerabilities in Microsoft Windows Server 2012

- [CVE-2025-59287](https://insights.sbomify.com/CVE-2025-59287/): Microsoft Windows Server Update Service (WSUS) Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2026-69595](https://insights.sbomify.com/CVE-2026-69595/): Windows Services for NFS ONCRPC XDR Driver Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2026-78445](https://insights.sbomify.com/CVE-2026-78445/): Windows Services for NFS ONCRPC XDR Driver Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2026-41089](https://insights.sbomify.com/CVE-2026-41089/): Windows Netlogon Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2024-43639](https://insights.sbomify.com/CVE-2024-43639/): Windows KDC Proxy Remote Code Execution Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27480 and fix it if it is affected.

What it is: CVE-2025-27480 is a high-severity use after free vulnerability in Microsoft Windows Server 2012, published on 8 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-27480 in the wild and no public exploit code.

Affected product: Microsoft Windows Server 2012. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-27480/ (Markdown: https://insights.sbomify.com/CVE-2025-27480/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-27480
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-27480
- OSV: https://osv.dev/vulnerability/CVE-2025-27480

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-27480/
Summaries are generated and may contain mistakes; the official description above is the record.