Taiwan Information Security Association

Security alertsSat, 14 Nov 2026

Microsoft November security update roundup: Windows LDAP and Windows Search

Microsoft rates two Windows vulnerabilities at CVSS v3.1 9.8. CVE-2026-119958 affects Windows LDAP, and CVE-2026-116928 affects Windows Search. Match each Windows product and release to Microsoft’s update and verify the running build.

01

Article

Microsoft disclosed separate remote code execution vulnerabilities in Windows LDAP and Windows Search on 10 November 2026. Both affect listed Windows client and server releases. Directory systems and their dependencies warrant particular attention for LDAP. Include enterprise workstations and servers in the Windows Search inventory according to Microsoft’s product list.

VulnerabilityWhat Microsoft discloses
CVE-2026-119958 · Windows LDAPAn out-of-bounds write can allow a network attacker to execute code. Microsoft CNA rates it CVSS v3.1 9.8.
CVE-2026-116928 · Windows SearchA separate out-of-bounds write can allow a network attacker to execute code. Microsoft CNA rates it CVSS v3.1 9.8.

Microsoft’s vectors specify network access, no prior privileges and no user interaction. Its CVE descriptions do not identify the network endpoint, port, service configuration or payload needed to trigger either flaw. Use Microsoft’s affected-product lists to determine update scope. CISA’s ADP assessments recorded no known exploitation for either vulnerability.

Attack flowWhat the two Microsoft disclosures establish
  1. 01

    Reach the vulnerable component over a network

    Microsoft lists network attack vectors for both Windows LDAP and Windows Search.

  2. 02

    Trigger the component’s memory write flaw

    The two vulnerabilities affect separate components. The exact request path and trigger are undisclosed.

  3. 03

    Execute code

    Successful exploitation could execute code in the affected Windows environment.

  4. 04

    Assess downstream impact

    Potential effects depend on host role, execution permissions, reachable services and data.

Affected builds and update boundaries

Microsoft’s CNA records list the same build boundaries for both CVEs. Affected builds for each listed product start at the first build shown and extend up to, but exclude, the fixed build. Use the applicable Microsoft entry for your edition, installation type and architecture. Check support and applicable servicing programs for older branches.

Windows product or branchAffected fromFixed build boundary
Windows 10 version 1607 / Windows Server 2016, including Server Core10.0.14393.010.0.14393.9688
Windows 10 version 1809 / Windows Server 2019, including Server Core10.0.17763.010.0.17763.9487
Windows 10 version 21H210.0.19044.010.0.19044.7846
Windows 10 version 22H210.0.19045.010.0.19045.7846
Windows 11 version 23H210.0.22631.010.0.22631.7711
Windows 11 version 24H210.0.26100.010.0.26100.9974
Windows 11 version 25H210.0.26200.010.0.26200.9974
Windows 11 version 26H110.0.28000.010.0.28000.3501
Windows 11 version 26H210.0.26300.010.0.26300.9974
Windows Server 202210.0.20348.010.0.20348.5870
Windows Server 2025, including Server Core10.0.26100.010.0.26100.33822
Response flowRecommended actions: from the perimeter to core systems
  1. 01

    Inventory Windows builds and review network access

    Record the product, release, architecture and full build on workstations, servers, remote desktops, virtual images, managed deployments and standby nodes. Identify which hosts provide critical directory services or support endpoint and server workflows.

    See what to doResources: 2

    TWISA member solutions

    Inventory Windows builds and review network access

    Use asset and vulnerability management to identify omitted hosts, reconcile actual builds with update inventory and track exceptions. Limit unnecessary reachability according to each host’s role.

  2. 02

    Deploy Microsoft updates for each release

    Use the matching Security Update Guide entry for the correct cumulative update. Test installation and any required restart, preserve directory service availability during rollout, and track managed Windows images and recovery environments.

    View guidanceResources: 2

    Response guidance

    Deploy Microsoft updates for each release

    Use the matching Security Update Guide entry for the correct cumulative update. Test installation and any required restart, preserve directory service availability during rollout, and track managed Windows images and recovery environments.

  3. 03

    Verify installed builds and essential functions

    Confirm the running build after any required restart. For directory environments, validate sign-in, directory lookups and replication where applicable. For endpoints and servers, check affected business workflows, including search and indexing where in use.

    See what to doResources: 2

    TWISA member solutions

    Verify installed builds and essential functions

    Endpoint and infrastructure controls can help confirm inventory and coverage. Identity services can help assess authentication dependencies during staged rollouts.

  4. 04

    Monitor and investigate unusual host or directory activity

    Correlate endpoint, Windows event, identity and network telemetry. Review abnormal process creation, unexpected access, service disruption and unusual outbound connections. If evidence indicates compromise, preserve records, isolate affected systems as appropriate and recover from trusted artifacts.

    See what to doResources: 2

    TWISA member solutions

    Monitor and investigate unusual host or directory activity

    Use monitoring to correlate signals over time. Incident responders can preserve evidence, scope affected systems and validate recovery.

Defense architectureProtect Windows endpoints and directory services across the deployment

Track product, architecture, OS build and operational role for all Windows assets, including outsourced and standby environments.

Allow authorized traffic and apply controls at each layer.

  1. 01

    Network and remote access

    Internet, internal segments and managed devices

    Limit exposureAllow only required connections and validate access by asset role.

  2. 02

    Windows endpoints and servers

    Windows client and server branches

    Install and verify updatesCheck the relevant release and actual running build.

  3. 03

    Directory and business services

    Authentication, directory dependencies and core workloads

    Preserve continuityStage updates, validate service dependencies and test recovery.

Feed logs and traffic data from each layer into monitoring and response.

  1. Correlate host and identity telemetryCompare network activity, Windows events and endpoint detections against normal behavior.
  2. Investigate and recoverPreserve evidence, contain confirmed impact and verify restoration from trusted artifacts.

Proactive testing and retesting

With authorization, discover Windows assets and validate update status through vulnerability scanning. Use penetration tests, API tests where relevant, and controlled attack simulations to verify defenses for exposed enterprise services. Retest service reachability and business functions after changes. If a separate web application is in scope, evaluate WAF request, alert, blocking and backend outcomes for that application. Check host privilege boundaries and access between internal systems separately.

TWISA member solutions

Official sources

For further product and service details, please contact the relevant TWISA members.

Advisory updated: 2026/11/14. Check the vendor’s latest information for product support and fixes.