Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-21246: CWE-122: Heap-based Buffer Overflow in Microsoft Windows 10 Version 1507

0
High
VulnerabilityCVE-2025-21246cvecve-2025-21246cwe-122cwe-125
Published: Tue Jan 14 2025 (01/14/2025, 18:04:52 UTC)
Source: CVE Database V5
Vendor/Project: Microsoft
Product: Windows 10 Version 1507

Description

Windows Telephony Service Remote Code Execution Vulnerability

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/14/2026, 08:06:12 UTC

Technical Analysis

CVE-2025-21246 is a heap-based buffer overflow vulnerability classified under CWE-122, found in the Windows Telephony Service component of Microsoft Windows 10 Version 1507 (build 10.0.10240.0). The flaw allows remote code execution without requiring privileges (PR:N) but does require user interaction (UI:R), such as the user accepting a call or similar telephony event. The vulnerability arises from improper handling of memory buffers within the Telephony Service, leading to a heap overflow condition that can be exploited by sending specially crafted network requests. Successful exploitation can result in arbitrary code execution with system-level privileges, compromising confidentiality, integrity, and availability of the affected system. The CVSS v3.1 base score is 8.8, indicating a high severity with network attack vector (AV:N), low attack complexity (AC:L), and full impact on confidentiality, integrity, and availability (C:H/I:H/A:H). No patches or mitigations have been officially released yet, and no exploits are known in the wild, but the vulnerability poses a significant risk due to its potential impact and ease of exploitation. The affected Windows 10 Version 1507 is an early release of Windows 10, which is largely out of mainstream support, increasing the risk for organizations still using legacy systems. The Telephony Service is often enabled in enterprise environments that rely on telephony integration, making this vulnerability particularly relevant for such deployments.

Potential Impact

For European organizations, this vulnerability poses a serious threat, especially to those still operating legacy Windows 10 Version 1507 systems. The ability for unauthenticated remote attackers to execute arbitrary code can lead to full system compromise, data breaches, ransomware deployment, or disruption of critical services. Telecommunications providers, call centers, and enterprises integrating telephony services are at heightened risk due to the direct involvement of the Telephony Service. The vulnerability could be leveraged to pivot within networks, escalate privileges, and access sensitive data, impacting confidentiality and integrity. Availability could also be affected if attackers deploy destructive payloads or cause system crashes. Given the lack of patches and the requirement for user interaction, social engineering or phishing campaigns could be used to trigger exploitation. The impact is amplified in sectors critical to European infrastructure, such as finance, healthcare, and government, where legacy systems are still in use and telephony services are integral to operations.

Mitigation Recommendations

1. Disable the Windows Telephony Service on all systems where it is not explicitly required to reduce the attack surface. 2. Implement strict network segmentation and firewall rules to limit exposure of telephony-related ports and services to untrusted networks. 3. Educate users about the risks of interacting with unsolicited telephony requests or calls, reducing the likelihood of user interaction exploitation. 4. Prioritize upgrading affected systems from Windows 10 Version 1507 to supported, fully patched Windows versions to eliminate the vulnerability. 5. Monitor network traffic for anomalous telephony service requests that could indicate exploitation attempts. 6. Prepare incident response plans specific to telephony service compromise scenarios. 7. Apply any forthcoming patches from Microsoft immediately upon release and test them in controlled environments before deployment. 8. Use endpoint detection and response (EDR) tools to detect unusual process behavior related to the Telephony Service. 9. Restrict administrative privileges and enforce least privilege principles to limit damage from potential exploitation.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
microsoft
Date Reserved
2024-12-10T23:54:12.926Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68c0c0d09ed239a66badfcf8

Added to database: 9/10/2025, 12:05:36 AM

Last enriched: 2/14/2026, 8:06:12 AM

Last updated: 3/22/2026, 5:21:22 PM

Views: 123

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses