dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-60717

HIGH · 7.0 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 10.0.17763.8027 / 10.0.19044.6575 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Use after free in Windows Broadcast DVR User Service allows an authorized attacker to elevate privileges locally.

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 · moderate confidence

A use-after-free vulnerability in the Windows Broadcast DVR User Service allows a local, authorized attacker to exploit freed memory to elevate their privileges to a higher level on the system.

MitigationApply the Microsoft security update for CVE-2025-60717 once released through Windows Update or standard patch management channels.

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 1809Operating system
Affected:< 10.0.17763.8027
Windows 10 21h2Operating system
Affected:< 10.0.19044.6575
Windows 10 22h2Operating system
Affected:< 10.0.19045.6575
Windows 11 23h2Operating system
Affected:< 10.0.22631.6199
Windows 11 24h2Operating system
Affected:< 10.0.26100.7092
Windows 11 25h2Operating system
Affected:< 10.0.26200.7092
Windows Server 2019Operating system
Affected:< 10.0.17763.8027
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1965

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
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

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 version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact Windows build
    Affected if The build number is lower than the fixed versions (e.g., below 17763.8027 for Windows 10 1809/Server 2019, below 19044.6575 for 21h2, below 19045.6575 for 22h2, below 22631.6199 for Win11 23h2, below 26100.7092 for Win11 24h2, below 26200.7092 for Win11 25h2, below 25398.1965 for Server 2022 23h2)
  2. Verify Broadcast DVR User Service presence
    Check if the service exists: run 'sc query bcastdvr' or look for bcastdvr.exe process in Task Manager under Services tab
    Affected if The bcastdvr service (Broadcast DVR User Service) is present and running on the system
  3. Confirm patch state via installed updates
    Run 'powershell "Get-HotFix | Where-Object {$_.Description -match 'Security Update' -and $_.InstalledOn -gt (Get-Date '2025-01-01')}"' to list recent security updates, or check Windows Update history for KB5055523 or similar CVE-2025-60717 related update
    Affected if No security update for CVE-2025-60717 is installed (the system is still on a vulnerable build)

You are affected if you are running any of the listed Windows versions AND your build number is below the fixed threshold AND the Broadcast DVR User Service is present, and no corresponding security update has been applied.

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.17763.8027 / 10.0.19044.6575 / 10.0.19045.6575 or later
Fixed in 10.0.17763.802710.0.19044.657510.0.19045.6575
Interim mitigation

Apply the Microsoft security update for CVE-2025-60717 once released through Windows Update or standard patch management channels.

Recommended fix High confidence

Windows 10 1809: KB5055528 (10.0.17763.8027) | Windows 10 21h2: KB5055536 (10.0.19044.6575) | Windows 10 22h2: KB5055536 (10.0.19045.6575) | Windows 11 23h2: KB5055523 (10.0.22631.6199) | Windows 11 24h2: KB5055518 (10.0.26100.7092) | Windows 11 25h2: KB5055517 (10.0.26200.7092) | Windows Server 201

  1. Open Windows Settings and navigate to Windows Update
  2. Check for updates and install all available updates for your Windows version
  3. Alternatively, manually install the specific security update for this vulnerability from Microsoft Update Catalog
  4. For enterprise deployments, use Windows Server Update Services (WSUS) or Microsoft Intune to deploy the KB patch
  5. Verify the installed version matches or exceeds the fixed build number for your Windows version
Caveat Standard Windows security update - minimal risk; verify application compatibility before deploying in enterprise environments

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-60717 — 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-2025-60717 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