dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-59515

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 exists in the Windows Broadcast DVR User Service where the service continues to reference memory after it has been freed. An authorized local attacker can exploit this memory corruption to achieve arbitrary code execution and elevate privileges to higher integrity levels.

MitigationApply the Microsoft security update for CVE-2025-59515 via Windows Update or enterprise patch management to remediate the use-after-free in the Broadcast DVR User Service.

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 installed Windows build version
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to display the full Windows build number
    Affected if The displayed build number is lower than the version thresholds: 17763.8027 (Windows 10 1809/Server 2019), 19044.6575 (Windows 10 21h2), 19045.6575 (Windows 10 22h2), 22631.6199 (Windows 11 23h2), 26100.7092 (Windows 11 24h2), 26200.7092 (Windows 11 25h2), or 25398.1965 (Server 2022 23h2)
  2. Identify exact Windows release version
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v DisplayVersion' to get the release name (such as 1809, 21h2, 22h2, 23h2)
    Affected if The release version matches one of the affected versions listed in the CVE and the build number from step 1 is below the corresponding threshold
  3. Verify Broadcast DVR User Service presence
    Run 'sc query broadcastdvr' or check Services.msc for a service named "Broadcast DVR User Service" to confirm the component exists on the system
    Affected if The service exists on the system and the Windows version falls within the affected version ranges from step 1

A system is affected if it runs any of the listed Windows 10, Windows 11, or Windows Server versions with a build number lower than the specified threshold and has the Broadcast DVR User Service present.

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-59515 via Windows Update or enterprise patch management to remediate the use-after-free in the Broadcast DVR User Service.

Recommended fix High confidence

Install the Microsoft security update for CVE-2025-59515 (refer to the corresponding KB article on MSRC)

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security update
  3. Alternatively, manually download the specific security update from the Microsoft Update Catalog matching your Windows version (KB reference from MSRC)
  4. Restart the system after the update is installed
  5. Verify the update was successfully applied by checking the installed updates list and confirming the version matches or exceeds: Windows 10 1809/Server 2019: 10.0.17763.8027 | Windows 10 21h2: 10.0.19044.6575 | Windows 10 22h2: 10.0.19045.6575 | Windows 11 23h2: 10.0.22631.6199 | Windows 11 24h2: 10.0.26100.7092 | Windows 11 25h2: 10.0.26200.7092 | Windows Server 2022 23h2: 10.0.25398.1965
Caveat Standard Windows update - no expected breaking changes for this security patch

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
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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