dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-34341

HIGH · 7.0 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 10.0.14393.9140 / 10.0.17763.8755 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
Double free in Windows Link-Layer Discovery Protocol (LLDP) 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 double-free memory corruption vulnerability exists in Windows Link-Layer Discovery Protocol (LLDP) service. The flaw allows a locally authenticated attacker to potentially corrupt memory and escalate privileges to higher integrity levels by triggering the double-free condition in the LLDP component.

MitigationApply Microsoft security updates for Windows LLDP when released. Prioritize patching systems where non-administrative users have local access, as the attacker requires local authentication.

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 1607Operating system
Affected:< 10.0.14393.9140
Windows 10 1809Operating system
Affected:< 10.0.17763.8755
Windows 10 21h2Operating system
Affected:< 10.0.19044.7291
Windows 10 22h2Operating system
Affected:< 10.0.19045.7291
Windows 11 23h2Operating system
Affected:< 10.0.22631.7079
Windows 11 24h2Operating system
Affected:< 10.0.26100.8390
Windows 11 25h2Operating system
Affected:< 10.0.26200.8390
Windows 11 26h1Operating system
Affected:< 10.0.28000.2113

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. Identify Windows version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact Windows build version.
    Affected if The installed build number falls below the thresholds: 14393.9140 (1607), 17763.8755 (1809), 19044.7291 (21h2), 19045.7291 (22h2), 22631.7079 (23h2), 26100.8390 (24h2), 26200.8390 (25h2), or 28000.2113 (26h1).
  2. Verify LLDP service status
    Run 'Get-Service LLDP' in PowerShell or check Services.msc for the 'Link-Layer Discovery Protocol' service to determine if it is enabled or running.
    Affected if The LLDP service is enabled or set to Automatic startup, as the vulnerability exists within this component.
  3. Confirm Windows edition
    Run 'winver' or check System Properties to confirm whether the system is an affected Windows 10 or Windows 11 edition (Pro, Enterprise, or Home).
    Affected if The system runs a Windows 10 or Windows 11 edition listed in the affected product versions.

A system is affected if it runs a Windows 10 or Windows 11 version with a build number below the specified threshold AND has the LLDP service 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.14393.9140 / 10.0.17763.8755 / 10.0.19044.7291 or later
Fixed in 10.0.14393.914010.0.17763.875510.0.19044.7291
Interim mitigation

Apply Microsoft security updates for Windows LLDP when released. Prioritize patching systems where non-administrative users have local access, as the attacker requires local authentication.

Recommended fix High confidence

Upgrade to Windows 10 1607 build 10.0.14393.9140+, Windows 10 1809 build 10.0.17763.8755+, Windows 10 21h2 build 10.0.19044.7291+, Windows 10 22h2 build 10.0.19045.7291+, Windows 11 23h2 build 10.0.22631.7079+, Windows 11 24h2 build 10.0.26100.8390+, Windows 11 25h2 build 10.0.26200.8390+, or Window

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Settings > Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest security updates
  4. Alternatively, manually install the specific KB update for this CVE from the Microsoft Update Catalog
  5. Restart the system after the update is applied
  6. Verify the version matches or exceeds the fixed build (e.g., 10.0.14393.9140 for Windows 10 1607, 10.0.17763.8755 for Windows 10 1809, etc.)
Caveat Standard Windows security update; minimal risk; ensure backups and compatibility testing for legacy systems before applying

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

Fix this in Windows 10 1607 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-2026-34341 — 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-34341 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