dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2026-50342

HIGH · 8.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.26100.8875 / 10.0.26200.8875 or later.
See remediation →
90/100
Remediation priority · Urgent
Zero-click 5 weeks old

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
Improper access control in Windows MIDI Service Module allows an authorized attacker to elevate privileges locally.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1mo ago

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

Improper access control in the Windows MIDI Service Module allows a locally authorized attacker to escalate privileges. The vulnerability stems from insufficient permission checks within the MIDI service component, enabling a user with basic system access to gain higher-level Windows privileges.

MitigationApply the relevant Microsoft security update for the Windows MIDI Service Module as soon as patches become available, and ensure standard least-privilege access controls are maintained on affected systems.

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 11 24h2Operating system
Affected:< 10.0.26100.8875
Windows 11 25h2Operating system
Affected:< 10.0.26200.8875
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269< 10.0.28000.2525

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
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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 11 build version
    Open Command Prompt or PowerShell and run: winver.exe (GUI) or (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion').CurrentBuildNumber
    Affected if Build number is less than 26100 (for 24h2), 26200 (for 25h2), or 28000 (for 26h1)
  2. Check full Windows version string
    Run 'systeminfo' or '(Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion').DisplayVersion' in PowerShell
    Affected if Version shows 24h2, 25h2, or 26h1 with a build below the fixed versions (26100.8875, 26200.8875, 28000.2269/2525)
  3. Verify MIDI Service presence
    Run 'Get-Service -Name Midi*' or 'Get-Service -DisplayName *MIDI*' in PowerShell to list MIDI-related services
    Affected if A MIDI service exists and is installed on the system
  4. Check MIDI Service status
    Run 'Get-Service -Name Midi* | Select-Object Name, Status, StartType' in PowerShell
    Affected if The MIDI service is present and running (Status equals 'Running')
  5. Check MIDI Service module file version
    Locate the MIDI service binary (typically in C:\Windows\System32\ or C:\Windows\SysWOW64\) and run 'Get-Item <path> | Select-Object VersionInfo | Format-List *' to obtain file version details
    Affected if The MIDI service module file version is present and exploitable based on the affected build ranges

A system is affected if it runs Windows 11 24h2, 25h2, or 26h1 with a build number below the fixed versions AND has the MIDI service installed and enabled.

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.26100.8875 / 10.0.26200.8875 / 10.0.28000.2269 or later
Fixed in 10.0.26100.887510.0.26200.887510.0.28000.2269
Interim mitigation

Apply the relevant Microsoft security update for the Windows MIDI Service Module as soon as patches become available, and ensure standard least-privilege access controls are maintained on affected systems.

Recommended fix Moderate confidence

Windows 11 24h2: 10.0.26100.8875 or later; Windows 11 25h2: 10.0.26200.8875 or later; Windows 11 26h1: 10.0.28000.2269 or later (or 10.0.28000.2525 or later)

  1. Check current Windows build version by running 'winver' or 'systeminfo | findstr /B /C:"OS Version"'
  2. Identify the Windows 11 version (24h2, 25h2, or 26h1) from the build number
  3. For Windows 11 24h2: Ensure build is 10.0.26100.8875 or higher
  4. For Windows 11 25h2: Ensure build is 10.0.26200.8875 or higher
  5. For Windows 11 26h1: Ensure build is 10.0.28000.2269 or higher, or 10.0.28000.2525 or higher
  6. Apply Windows updates via Settings > Windows Update > Check for updates
  7. Restart the system after updates are installed
  8. Verify the updated build version matches the minimum required build for your version channel
Caveat Standard Windows update risks apply - ensure critical data is backed up before applying updates

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

Fix this in Windows 11 24h2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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