CVE-2026-62725 is a use-after-free in the Windows Telephony Service that allows local privilege escalation from an authenticated user context. The vulnerability is exploitable when an attacker can interact with the telephony subsystem's RPC interfaces—capabilities available to any user with logon rights on a multi-user Windows system, which substantially widens the practical attack surface beyond what the 'authorized attacker' language might imply. This is not merely a memory safety defect in isolation; the pattern of UAFs recurring in this service across years of patching suggests the underlying state management architecture creates persistent conditions for this vulnerability class. The CVSS 7 score reflects the technical severity of a single flaw but does not capture the compounding risk of a service where object lifecycle boundaries have become unclear through decades of feature accumulation. The EPSS score of 0.00204 indicates low short-term exploitation probability, though this reflects the requirement for local access rather than inherent difficulty—organizations should treat this as a reminder that legacy services at trust boundaries warrant architectural review rather than just point patches. Defenders should verify that telephony-related RPC endpoints are appropriately restricted, monitor for unexpected telephony service interactions from non-service accounts, and flag this service for prioritized patching given the pattern history. The deeper question is whether Microsoft should refactor the authorization model between callers and the Telephony Service itself—specifically, whether the service correctly validates caller context across asynchronous operations rather than assuming that context remains stable. This is the architectural weakness that enables UAFs to become privilege escalation vectors in this component, and point patches alone have not resolved it across multiple prior instances.
CVE-2026-62725
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 · uneditedUse after free in Windows Telephony Service allows an authorized attacker to elevate privileges locally.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
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 analysisMemory is used after it has been freed, so its contents — now potentially attacker-controlled — drive the program's behaviour. With careful heap grooming this becomes code execution. The fix requires disciplined ownership of memory and often a targeted rework of the object lifecycle.
General guidance for the use after free class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
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< 10.0.14393.9418< 10.0.17763.9121< 10.0.19044.7663< 10.0.19045.7663< 10.0.22631.7517< 10.0.26100.9106< 10.0.26200.9106< 10.0.28000.2704CVSS 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
- Local
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
From vendor data10.0.14393.941810.0.17763.912110.0.19044.7663
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-62725 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesCVE-2026-62725 is a use-after-free in the Windows Telephony Service that allows local privilege escalation from an authenticated user context. The vulnerability is exploitable when an attacker can interact with the telephony subsystem's RPC interfaces—capabilities available to any user with logon rights on a multi-user Windows system, which substantially widens the practical attack surface beyond what the 'authorized attacker' language might imply. This is not merely a memory safety defect in isolation; the pattern of UAFs recurring in this service across years of patching suggests the underlying state management architecture creates persistent conditions for this vulnerability class. The CVSS 7 score reflects the technical severity of a single flaw but does not capture the compounding risk of a service where object lifecycle boundaries have become unclear through decades of feature accumulation. The EPSS score of 0.00204 indicates low short-term exploitation probability, though this reflects the requirement for local access rather than inherent difficulty—organizations should treat this as a reminder that legacy services at trust boundaries warrant architectural review rather than just point patches. Defenders should verify that telephony-related RPC endpoints are appropriately restricted, monitor for unexpected telephony service interactions from non-service accounts, and flag this service for prioritized patching given the pattern history. The deeper question is whether Microsoft should refactor the authorization model between callers and the Telephony Service itself—specifically, whether the service correctly validates caller context across asynchronous operations rather than assuming that context remains stable. This is the architectural weakness that enables UAFs to become privilege escalation vectors in this component, and point patches alone have not resolved it across multiple prior instances.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-62725 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
- 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