dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-25188

HIGH · 8.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 10.0.14393.8957 / 10.0.17763.8511 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Heap-based buffer overflow in Windows Telephony Service allows an unauthorized attacker to elevate privileges over an adjacent network.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence

Heap-based buffer overflow vulnerability in Windows Telephony Service enables an unauthenticated attacker with adjacent network access to achieve privilege escalation. The flaw allows overflow of heap-allocated memory, potentially permitting arbitrary code execution with elevated system privileges.

MitigationApply Microsoft security patches for Windows Telephony Service when available; restrict network access to affected systems via network segmentation to limit adjacent network attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1607Operating system
Affected:< 10.0.14393.8957
Windows 10 1809Operating system
Affected:< 10.0.17763.8511
Windows 10 21h2Operating system
Affected:< 10.0.19044.7058
Windows 10 22h2Operating system
Affected:< 10.0.19045.7058
Windows 11 23h2Operating system
Affected:< 10.0.22631.6783
Windows 11 24h2Operating system
Affected:< 10.0.26100.7979
Windows 11 25h2Operating system
Affected:< 10.0.26200.7979
Windows 11 26h1Operating system
Affected:< 10.0.28000.1719

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows build version
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to view the full build number (e.g., 10.0.19045.7058)
    Affected if The build number falls below any of these thresholds: 14393.8957, 17763.8511, 19044.7058, 19045.7058, 22631.6783, 26100.7979, 26200.7979, or 28000.1719 depending on your Windows release
  2. Verify Telephony Service status
    Open PowerShell and run 'Get-Service -Name "TapiSrv" -ErrorAction SilentlyContinue' or 'sc query TapiSrv' to check if the Windows Telephony Service is installed and running
    Affected if The service state shows as Running and your Windows build is below the fixed versions listed above
  3. Confirm Windows release version
    Run 'winver' to identify if you are on Windows 10 1607, 1809, 21h2, 22h2, or Windows 11 23h2, 24h2, 25h2, or 26h1, then cross-reference with the affected build ranges provided in the CVE
    Affected if Your specific Windows release matches one of the affected versions AND your installed build is lower than the corresponding fixed build for that release

You are affected if your Windows build version is below the threshold for your specific Windows release AND the Telephony Service (TapiSrv) is present and enabled on your system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.14393.8957 / 10.0.17763.8511 / 10.0.19044.7058 or later
Fixed in 10.0.14393.895710.0.17763.851110.0.19044.7058
Interim mitigation

Apply Microsoft security patches for Windows Telephony Service when available; restrict network access to affected systems via network segmentation to limit adjacent network attack surface.

Recommended fix High confidence

Upgrade to Windows 10 build 10.0.14393.8957 or later (1607), 10.0.17763.8511 or later (1809), 10.0.19044.7058 or later (21h2), 10.0.19045.7058 or later (22h2); or Windows 11 build 10.0.22631.6783 or later (23h2), 10.0.26100.7979 or later (24h2), 10.0.26200.7979 or later (25h2), 10.0.28000.1719 or la

  1. Identify the current Windows version by running 'winver' or 'systeminfo' from command prompt
  2. Determine the applicable Windows release (e.g., Windows 10 1809, Windows 11 23h2) from the version number
  3. For Windows 10: Navigate to Settings > Update & Security > Windows Update and install all available updates
  4. For Windows 11: Navigate to Settings > Windows Update and install all available updates
  5. Alternatively, manually download and install the specific security update for your Windows version from the Microsoft Update Catalog (search for the CVE KB number)
  6. After installation, restart the system to apply the security update
  7. Verify the installation by checking that the Windows version matches or exceeds the fixed build number for your release
Caveat Standard Windows update; no major breaking changes expected but verify critical applications are compatible before deployment in enterprise environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25188 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25188 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data