First published: Tue Feb 11 2025(Updated: )
Windows Routing and Remote Access Service (RRAS) Remote Code Execution Vulnerability
Credit: secure@microsoft.com
Affected Software | Affected Version | How to fix |
---|---|---|
Microsoft Windows Server 2012 x64 | ||
Microsoft Windows Server 2012 x64 | ||
Microsoft Windows Server 2022 23H2 | ||
Microsoft Windows Server 2008 R2 | ||
Microsoft Windows Server 2022 | ||
Microsoft Windows Server 2022 | ||
Microsoft Windows Server 2012 R2 | ||
Microsoft Windows Server 2019 | ||
Microsoft Windows Server 2008 Itanium | ||
Microsoft Windows Server 2008 R2 | ||
Microsoft Windows Server 2016 | ||
Microsoft Windows Server 2008 Itanium | ||
Microsoft Windows Server 2016 | ||
Microsoft Windows Server 2025 | ||
Microsoft Windows Server 2012 R2 | ||
Microsoft Windows Server 2008 Itanium | ||
Microsoft Windows Server 2019 | ||
Microsoft Windows Server 2025 | ||
Microsoft Windows Server 2008 Itanium | ||
Microsoft Windows Server 2008 Itanium | =sp2 | |
Microsoft Windows Server 2008 Itanium | =sp2 | |
Microsoft Windows Server 2008 Itanium | =r2-sp1 | |
Microsoft Windows Server 2012 x64 | ||
Microsoft Windows Server 2012 x64 | =r2 | |
Microsoft Windows Server 2016 | <10.0.14393.7785 | |
Microsoft Windows Server 2019 | <10.0.17763.6893 | |
Microsoft Windows Server 2022 | <10.0.20348.3207 | |
Microsoft Windows Server 2022 23H2 | <10.0.25398.1425 | |
Microsoft Windows Server 2025 | <10.0.26100.3194 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-21410 is rated as a critical severity vulnerability due to its potential for remote code execution.
You can fix CVE-2025-21410 by applying the recommended security patches provided by Microsoft for the affected Windows Server versions.
CVE-2025-21410 affects several versions of Windows Server, including 2012, 2012 R2, 2016, 2019, 2022, and 2025.
If exploited, CVE-2025-21410 allows an attacker to execute arbitrary code on the target system remotely.
Currently, Microsoft recommends updating to resolve CVE-2025-21410, as no formal workarounds have been published.