Skip to content
Fencer Vulns
high 8.1

CVE-2024-49106 json

Windows Remote Desktop Services Remote Code Execution Vulnerability

published 2024-12-10 22 mo ago modified 2026-06-17 4 mo ago also EUVD-2024-43794

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits
0
none known

Summary

Windows Remote Desktop Services Remote Code Execution Vulnerability

Patch / fix

  • Microsoft Windows Server 2016 10.0.14393.7606
  • Microsoft Windows Server 2016 (Server Core installation) 10.0.14393.7606
  • Microsoft Windows Server 2019 10.0.17763.6659
  • Microsoft Windows Server 2019 (Server Core installation) 10.0.17763.6659
  • Microsoft Windows Server 2022 10.0.20348.2966
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation) 10.0.25398.1308
  • Microsoft Windows Server 2025 10.0.26100.2605
  • Microsoft Windows Server 2025 (Server Core installation) 10.0.26100.2605

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
22 mo ago

Exploit prediction

1.21% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 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
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2016 (Server Core installation)
  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2019 (Server Core installation)
  • Microsoft Windows Server 2022
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)
  • Microsoft Windows Server 2025
  • Microsoft Windows Server 2025 (Server Core installation)

Classification

Weakness
  • CWE-591 Sensitive Data Storage in Improperly Locked Memory
  • CWE-416 Use After Free
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.