CVE-2026-34349
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 · uneditedExposure of sensitive information to an unauthorized actor in Windows Media allows an authorized attacker to disclose information locally.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
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 confidenceThis is a local information disclosure vulnerability in Windows Media that allows an authorized attacker to access sensitive information they should not have access to. The vulnerability requires local access rather than remote exploitation, and the attacker must already have some level of authorization to the system.
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< 10.0.17763.9020< 10.0.19044.7548< 10.0.19045.7548< 10.0.26100.8875< 10.0.26200.8875< 10.0.28000.2269< 10.0.17763.9020< 10.0.20348.5386CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows build versionRun 'winver' from command prompt or 'systeminfo' and locate the 'OS Version' or 'Build' lineAffected if The build number is lower than the threshold for your Windows version (17763.9020 for 1809/Server 2019, 19044.7548 for 21h2, 19045.7548 for 22h2, 26100.8875 for 11 24h2, 26200.8875 for 11 25h2, 28000.2269 for 11 26h1, or 20348.5386 for Server 2022)
-
Verify Windows Media component is presentCheck for Windows Media Player by searching for 'Windows Media Player' in Start menu, or check for the file 'wmplayer.exe' in C:\Windows\System32 or C:\Program Files\Windows Media PlayerAffected if Windows Media Player executable exists on the system and the Windows version is below the fixed build for your release
-
Confirm Windows Media DLL versions (optional)If Windows Media Player is present, right-click wmplayer.exe in File Explorer, select Properties, and view the 'Product version' field under the Details tabAffected if The product version shown is older than the fixed version corresponding to your Windows build
Your system is affected if it runs any of the listed Windows versions below the specified build numbers AND has Windows Media component installed or enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.17763.902010.0.19044.754810.0.19045.7548
Apply the relevant Microsoft security update for Windows Media when available. Until then, limit local access to trusted personnel and monitor for unusual access patterns to Windows Media components.
Upgrade to Windows 10 build 19045.7548 or later for 22h2; build 19044.7548 or later for 21h2; build 17763.9020 or later for 1809/Server 2019; Windows 11 build 26100.8875 or later for 24h2; build 26200.8875 or later for 25h2; build 28000.2269 or later for 26h1; Windows Server 2022 build 20348.5386 or
- Identify the current Windows version by running 'winver' or 'systeminfo' to confirm which version and build number is currently installed
- Determine the minimum required build for your Windows version from the affected versions list
- Open Windows Settings > Update & Security > Windows Update
- Click 'Check for updates' and ensure all updates are downloaded and installed
- Alternatively, for enterprise environments, deploy the relevant Security Update via Windows Server Update Services (WSUS) or Microsoft Intune
- Verify the installation was successful by checking the OS build number matches or exceeds the required version: 10.0.17763.9020 (1809/Server 2019), 10.0.19044.7548 (21h2), 10.0.19045.7548 (22h2), 10.0.26100.8875 (24h2), 10.0.26200.8875 (25h2), 10.0.28000.2269 (26h1), or 10.0.20348.5386 (Server 2022)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34349 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34349 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
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.
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