Microsoft Windows up to Server 2025 Telephony Service heap-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.1 | $5k-$25k | 0.00 |
Summary
A vulnerability classified as critical has been found in Microsoft Windows. The impacted element is an unknown function of the component Telephony Service. The manipulation leads to heap-based overflow. This vulnerability is uniquely identified as CVE-2026-25188. The attack can only be initiated within the local network. No exploit exists. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability was found in Microsoft Windows. It has been rated as critical. This issue affects some unknown processing of the component Telephony Service. The manipulation with an unknown input leads to a heap-based overflow vulnerability. Using CWE to declare the problem leads to CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Heap-based buffer overflow in Windows Telephony Service allows an unauthorized attacker to elevate privileges over an adjacent network.
The weakness was disclosed 03/10/2026 as confirmed security update guide (Website). It is possible to read the advisory at msrc.microsoft.com. The identification of this vulnerability is CVE-2026-25188. The exploitation is known to be easy. Access to the local network is required for this attack to succeed. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 03/13/2026).
The vulnerability scanner Nessus provides a plugin with the ID 301776 (KB5078883: Windows 11 version 23H2 Security Update (March 2026)), which helps to determine the existence of the flaw in a target environment.
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (301776). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 10 21H2
- 10 22H2
- 10 1607
- 10 1809
- 11 23H2
- 11 24H2
- 11 25H2
- 11 26H1
- Server 2012
- Server 2012 R2
- Server 2016
- Server 2019
- Server 2022
- Server 2022 23H2
- Server 2025
License
Website
- Vendor: https://www.microsoft.com/
- Product: https://www.microsoft.com/en-us/windows
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.8VulDB Meta Temp Score: 8.1
VulDB Base Score: 8.8
VulDB Temp Score: 7.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 8.8
Vendor Vector (Microsoft): 🔒
CNA Base Score: 8.8
CNA Vector (Microsoft): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Heap-based overflowCWE: CWE-122 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Unproven
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 301776
Nessus Name: KB5078883: Windows 11 version 23H2 Security Update (March 2026)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒
Timeline
03/10/2026 VulDB entry created03/10/2026 Advisory disclosed
03/10/2026 Countermeasure disclosed
03/13/2026 VulDB entry last update
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2026-25188 (🔒)
GCVE (CVE): GCVE-0-2026-25188
GCVE (VulDB): GCVE-100-350027
scip Labs: https://www.scip.ch/en/?labs.20161215
Entry
Created: 03/10/2026 19:20Updated: 03/13/2026 07:01
Changes: 03/10/2026 19:20 (26), 03/10/2026 19:21 (10), 03/10/2026 19:24 (33), 03/11/2026 19:33 (2), 03/13/2026 07:01 (12)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.