CVE-2025-24056

Windows Telephony Service Remote Code Execution Vulnerability

HIGH
8.8
CVSS Score
Published: March 11, 2025 at 04:59 PM UTC
Updated: June 17, 2026 at 08:57 AM UTC
16 products affected across 1 vendorWindows Server 2016Windows Server 2019Windows Server 2012

Using Windows 10 Version 1809 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows 10 Version 1809 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 2%
SSVC
No known exploit

Description

Heap-based buffer overflow in Windows Telephony Server allows an unauthorized attacker to execute code over a network.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 10.0.10240.2094710.0.10240.0 ≤ v < 10.0.10240.2094710.0.10240.0
Affected range stops below 10.0.10240.20947, so it looks safe — our inference, not a vendor statement
v < 10.0.14393.787610.0.14393.0 ≤ v < 10.0.14393.787610.0.14393.0
Affected range stops below 10.0.14393.7876, so it looks safe — our inference, not a vendor statement
v < 10.0.17763.700910.0.17763.0 ≤ v < 10.0.17763.700910.0.17763.0
Affected range stops below 10.0.17763.7009, so it looks safe — our inference, not a vendor statement
v < 10.0.19044.560810.0.19044.0 ≤ v < 10.0.19044.560810.0.19044.0
Affected range stops below 10.0.19044.5608, so it looks safe — our inference, not a vendor statement
v < 10.0.19045.560810.0.19045.0 ≤ v < 10.0.19045.560810.0.19045.0
Affected range stops below 10.0.19045.5608, so it looks safe — our inference, not a vendor statement
v < 10.0.22621.503910.0.22621.0 ≤ v < 10.0.22621.503910.0.22621.0
Affected range stops below 10.0.22621.5039, so it looks safe — our inference, not a vendor statement
v < 10.0.22631.503910.0.22631.0 ≤ v < 10.0.22631.503910.0.22631.0
Affected range stops below 10.0.22631.5039, so it looks safe — our inference, not a vendor statement
v < 10.0.26100.340310.0.26100.0 ≤ v < 10.0.26100.347610.0.26100.3403 < v < 10.0.26100.347610.0.26100.0
Affected range stops below 10.0.26100.3403, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.26100.3476, so it looks safe — our inference, not a vendor statement
6.0.6003.0 ≤ v < 6.0.6003.231686.1.7601.0 ≤ v < 6.1.7601.276186.0.6003.06.1.7601.0r2 sp1sp2
Affected range stops below 6.0.6003.23168, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.7601.27618, so it looks safe — our inference, not a vendor statement
v < 6.2.9200.253686.2.9200.0 ≤ v < 6.2.9200.253686.3.9600.0 ≤ v < 6.3.9600.224706.2.9200.06.3.9600.0r2
Affected range stops below 6.2.9200.25368, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.3.9600.22470, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHmicrosoft
Vector?

Quick Info

StatusANALYZED
CWE
CWE-122

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card