From the CrowdStrike edition of November 10, 2026
CrowdStrike's November 2026 Patch Tuesday analysis: an exploited Outlook zero-day and zero-click flaws in Exchange search indexing and Windows LDAP
CrowdStrike Falcon Exposure Management team · Vulnerability management (cross-sector) · Global
- Publisher
- CrowdStrike blog
- Original publication
- November 10, 2026
- Source retrieved
- 2026-11-11
- Event date
- 2026-11-10
What happened
CrowdStrike counts 1,252 Microsoft fixes this month, including one exploited zero-day and 68 Critical vulnerabilities, with 745 Windows patches and 658 for Extended Security Updates (ESU). It highlights the exploited Outlook spoofing flaw CVE-2026-124194 that leaks NTLMv2 hashes when a crafted file is opened, CVE-2026-116928 in Windows Search that Exchange triggers when indexing an emailed attachment with no user action, CVE-2026-119958 unauthenticated remote code execution in Windows LDAP on domain controllers, eight preview-pane Office flaws and 14 unauthenticated network-reachable remote code execution flaws in legacy services such as MSMQ. Independent outlets report a lower total of about 1,093 to 1,094; CrowdStrike does not explain its counting.
Why it matters
Government and school networks rely on Active Directory and Outlook, many still run on-premises Exchange, and older Windows fleets on ESU are common in agencies and districts. Zero-click paths through mail servers and domain controllers are the highest-impact items for small public IT teams this month.
Evidence and measured results
Opened the full CrowdStrike blog (Nov 10). CVE details match Microsoft's advisories as quoted by The Register; the headline total differs from Krebs and The Register, likely because of counting choices that CrowdStrike does not state.
Limitations and uncertainty
Vendor analysis; total count differs from independent reporting without explanation; no exploitation data beyond Microsoft's single exploited flag.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-11; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Record patch volumes overwhelm small public IT teams that must decide what to fix first.
- Stakeholders
- IT director or CIO
- Systems administrators
- Identity or Active Directory owner
- Messaging administrator
- Discovery questions
- Do you still run on-premises Exchange?
- How long does it take to patch all domain controllers?
- How many devices depend on Extended Security Updates?
- Value hypothesis
- Exposure-based prioritization may shorten time to patch the highest-impact systems; no measured SLED results are offered.
- Potential engagement
- A one-cycle patch prioritization and exposure review focused on mail servers and domain controllers.
- Unsupported claims
- That 1,252 is the definitive count
- That any product removes the need to patch
- Exploitation of the zero-click flaws in the wild
Pre-sales engineering
Role takeaway
- Fit
- Microsoft-centric agencies, campuses and districts, especially with on-premises Exchange or ESU fleets.
- Architecture and integration
- Use vulnerability management and endpoint telemetry to rank fixes by exposure and exploitation, feeding existing patch tooling.
- Prerequisites
- Inventory of Exchange servers and domain controllers
- Patch deployment tooling
- Device inventory with ESU status
- Constraints
- Change windows during school terms or elections
- Legacy hardware on ESU
- Testing time for domain controller patches
- Security
- Prioritize the exploited Outlook NTLM leak and zero-click Exchange and LDAP flaws; restrict outbound NTLM where possible.
- Proof of value
- Domain controllers patched within an agreed window
- Outbound NTLM to external hosts blocked in test
- Patch status reported for all ESU devices
Delivery
Role takeaway
- Work
- Ranked patch plan for the cycle with tracking and exceptions.
- Dependencies
- Change approval
- Patch tooling
- Asset inventory
- Ownership
- Infrastructure operations under the CISO.
- Skills and adoption
- Staff trained on risk-based prioritization over severity-only lists.
- Governance checkpoints
- Priority list approved
- Seven-day coverage review
- Exceptions signed off
- Acceptance criteria
- Proposed: all domain controllers and Exchange servers patched within 14 days
- Proposed: exceptions documented with compensating controls
- Risks
- Patch-induced outages on domain controllers
- Missed legacy servers
- Confusion from differing CVE counts
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
On-premises Exchange and domain controllers are the priority; organizations on Exchange Online still need to patch Windows Search where Exchange servers remain.
Governance
Who approves, reviews and stays accountable for outcomes?
Monthly volumes above 1,000 fixes make CVSS-only prioritization impractical; risk-based ordering by exposure and exploitation needs documented approval.
Security and privacy
What data, permissions and controls need testing?
NTLM hash disclosure and domain controller compromise put identity, and therefore resident and student records, at risk.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Patch volume at this scale strains small teams and argues for automation and shared services.
Procurement
What should contracts, pricing and exit terms secure?
ESU-dependent fleets carry continued patch burden and cost; this is a reason to revisit hardware refresh timing.
Operating model
Which teams own the service once it runs?
Patching becomes a continuous triage function rather than a monthly event.
Publication history
- 2026-11-10CrowdStrike · Issue 134 resources
Stable resource ID: crowdstrike-november-2026-patch-tuesday-analysis-2026-11-10