dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2026-23667

HIGH · 7.0 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 10.0.17763.8511 / 10.0.19044.7058 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 Broadcast DVR 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

Use-after-free vulnerability in Broadcast DVR component allows an authorized local attacker to manipulate memory after deallocation and achieve privilege escalation. The vulnerability stems from improper memory management in the DVR software that can be exploited to gain higher-level system access.

MitigationApply available security updates for the Broadcast DVR component; if no patch exists, implement compensating controls such as restricting local access to trusted personnel and monitoring for suspicious process behavior.

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.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
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 build number
    Run 'winver' from command prompt or check 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build number
    Affected if The build number falls below any of these thresholds: 10.0.17763.8511 (Win10 1809), 10.0.19044.7058 (Win10 21h2), 10.0.19045.7058 (Win10 22h2), 10.0.22631.6783 (Win11 23h2), 10.0.26100.7979 (Win11 24h2), 10.0.26200.7979 (Win11 25h2), or 10.0.28000.1719 (Win11 26h1)
  2. Identify Broadcast DVR service status
    Run 'Get-Service -Name *DVR*' or 'Get-Service -Name *Broadcast*' in PowerShell to enumerate DVR-related services
    Affected if Any Broadcast DVR service is installed and running on the system
  3. Check for DVR executable process
    Run 'Get-Process | Where-Object {$_.ProcessName -like "*DVR*" -or $_.ProcessName -like "*Broadcast*"}' in PowerShell to list active DVR processes
    Affected if A Broadcast DVR process is currently running
  4. Verify DVR feature is enabled
    Run 'Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -like "*DVR*" -or $_.FeatureName -like "*Broadcast*"}' in PowerShell to check feature state
    Affected if The Broadcast DVR Windows feature is in an enabled state

A system is affected if it runs a Windows version with a build number below the thresholds AND has the Broadcast DVR component enabled or running.

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.8511 / 10.0.19044.7058 / 10.0.19045.7058 or later
Fixed in 10.0.17763.851110.0.19044.705810.0.19045.7058
Interim mitigation

Apply available security updates for the Broadcast DVR component; if no patch exists, implement compensating controls such as restricting local access to trusted personnel and monitoring for suspicious process behavior.

Recommended fix High confidence

Install the latest Windows Cumulative Update for your specific version (minimum: Windows 10 1809 build 17763.8511, Windows 10 21h2 build 19044.7058, Windows 10 22h2 build 19045.7058, Windows 11 23h2 build 22631.6783, Windows 11 24h2 build 26100.7979, Windows 11 25h2 build 26200.7979, Windows 11 26h1

  1. Open Windows Settings and navigate to Windows Update, or run 'ms-settings:windowsupdate'
  2. Click 'Check for updates' and install all available updates
  3. Alternatively, manually download and install the appropriate Cumulative Update for your Windows version from the Microsoft Update Catalog
  4. Ensure the installed build number meets or exceeds the fixed version for your Windows release
  5. Restart the system after applying updates
  6. Verify the installed version by running 'winver' or 'systeminfo | findstr /B /C:"OS Version"'
Caveat Standard Windows update process; 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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
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,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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