Security readout for executives and security teams
Plain-English summary
A logged-in attacker with limited existing access could abuse a memory-management flaw in Windows LLDP to gain higher privileges. Successful exploitation could compromise confidentiality, integrity, and availability. The attack is local, requires privileges, and has high complexity, which reduces—but does not eliminate—business risk.
Executive priority
Treat as a high-priority patching issue, especially where untrusted or numerous low-privilege users have local access. It is not described as remotely exploitable or actively exploited. Address it within the normal high-severity remediation window, accelerating critical shared systems and environments with weak account controls.
Technical view
CVE-2026-34341 is a CWE-415 double-free vulnerability in Windows Link-Layer Discovery Protocol. Its CVSS 3.1 score is 7.0 (high): local access, high attack complexity, low privileges, and no user interaction are required. Successful exploitation can produce high confidentiality, integrity, and availability impact without changing security scope.
Likely exposure
Exposure spans the listed Windows 10, Windows 11, and Windows Server releases, including several Server Core installations. Organizations should compare deployed editions, versions, and patch status with Microsoft's advisory. The source bundle does not establish whether LLDP configuration changes exposure.
Exploitation context
The attacker must already be authorized locally with low privileges, and exploitation has high complexity. No user interaction is required. The source bundle marks the CVE as absent from KEV and provides no cited evidence of active exploitation; this does not prove exploitation is impossible or nonexistent.
Researcher notes
The supplied evidence identifies the vulnerable condition as a double free but does not describe the affected code path, trigger, exploitation mechanics, mitigations, or specific update identifiers. Avoid assuming LLDP can simply be disabled or that disabling it fully mitigates exposure; verify all remediation and applicability details in Microsoft's advisory.
Mitigation direction
- Review Microsoft's CVE advisory for applicable security updates and deployment requirements.
- Apply the relevant Microsoft security updates to affected, supported Windows systems.
- Prioritize privileged workstations, shared servers, and systems where low-privilege users can authenticate.
- Use normal change control and test updates before broad production deployment.
Validation and detection
- Inventory Windows editions, versions, build numbers, and Server Core installations.
- Compare each system against Microsoft's affected-product and security-update information.
- Confirm applicable updates installed successfully and systems completed any required restart.
- Re-scan patched assets and investigate update failures or unsupported affected systems.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-415: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-34341 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C15.9microsoftVulnerability scoring details
Base CVSS 3.1 score
7HighVector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Windows Link-Layer Discovery Protocol (LLDP) Elevation of Privilege VulnerabilityCVE reference, microsoft · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Double Free
Double Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.