Security readout for executives and security teams
Plain-English summary
A network-connected attacker who already has authorized, low-level access could use an alternate TCP/IP path to bypass a Windows security control and make unauthorized changes. The issue affects numerous supported and legacy Windows desktop and server releases. The supplied evidence indicates integrity risk, but not data disclosure or service disruption.
Executive priority
Schedule remediation through the normal security-update cycle, accelerating internet-facing, shared, or sensitive Windows servers. Although rated medium and lacking evidence of exploitation, the potential for high-integrity impact means exposed systems should not remain unpatched. Track exceptions until Microsoft guidance confirms protection.
Technical view
CVE-2026-35422 is a Windows TCP/IP Driver security-feature bypass classified as CWE-288. Its CVSS 3.1 score is 6.5: network-accessible, low complexity, low privileges, no user interaction, unchanged scope, high integrity impact, and no stated confidentiality or availability impact. Public sources supplied here do not describe the bypassed control or protocol conditions.
Likely exposure
Exposure exists on listed Windows 10, Windows 11, and Windows Server versions when reachable over a network by an authorized low-privilege attacker. Actual exposure depends on installed security updates and unspecified environmental prerequisites. The source bundle does not identify particular ports, services, roles, or configurations required.
Exploitation context
The CVSS exploit-maturity value is unproven, and the vulnerability is not identified as CISA KEV in the supplied bundle. No cited evidence establishes active exploitation or a public proof of concept. Exploitation requires an authorized attacker with low privileges and network access; further mechanics are not publicly detailed here.
Researcher notes
The public record establishes CWE-288 and an alternate-path authentication bypass but omits the affected security feature, packet flow, prerequisites, and vulnerable code path. Duplicate capitalization variants appear for Windows 11 23H2. Treat the listed version numbers as product identifiers from the record; use Microsoft’s advisory for precise update applicability.
Mitigation direction
- Review the Microsoft advisory for applicable security updates and deployment requirements.
- Prioritize affected network-reachable servers and systems accessible to low-privilege users.
- Apply Microsoft-provided updates through the organization’s established patch-management process.
- Use network segmentation and least privilege to reduce reachable attack paths pending remediation.
Validation and detection
- Inventory listed Windows editions and compare installed builds and updates with Microsoft guidance.
- Confirm affected endpoints received the applicable Microsoft security update successfully.
- Rescan patched systems and investigate update failures, exclusions, or pending restarts.
- Document systems that cannot be updated and verify compensating access restrictions.
Public sources used
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-288: 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access 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-35422 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
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N/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:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N/E:U/RL:O/RC:C2.83.6microsoftVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N/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 TCP/IP Driver Security Feature Bypass 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.
Authentication Bypass Using an Alternate Path or Channel
Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.