Microsoft’s September 2026 Patch Tuesday addresses 964 CVEs (CVE-2026-81963,...

Executive Summary

104 Critical 860 Important 0 Moderate 0 Low Microsoft addresses 964 CVEs, smashing July’s release as the largest Patch Tuesday release. This month’s updates include patches for two zero-days that were exploited in the wild. Microsoft patched a record 964 CVEs in its September 2026 Patch Tuesday release, with 104 rated critical and 860 rated as important. This month’s update includes patches for: .NET .NET and Visual Studio ASP.NET Core Active Directory Certificate Services (AD CS) Active Directory Domain Services Active Directory Federation Services (AD FS) Audio Video Control Transport Protocol Azure Arc Azure CycleCloud Azure HDInsights BranchCache Connected Devices Platform Service (Cdpsvc) Data Sharing Service Client GitHub Copilot and Visual Studio Code Graphic Fonts HID class driver IP Helper Internet Storage Name Service Kernel Streaming WOW Thunk Service Driver Microsoft Account Microsoft Authenticator Microsoft Azure Attestation service and Device Health Attestation Service Microsoft Azure CLI Microsoft COM for Windows Microsoft Dynamics 365 Microsoft Exchange Server Microsoft Graphics Component Microsoft Install Service Microsoft JScript Microsoft Local Security Authority Server (lsasrv) Microsoft Office Microsoft Office Access Microsoft Office Excel Microsoft Office Outlook Microsoft Office PowerPoint Microsoft Office Publisher Microsoft Office SharePoint Microsoft Office Word Microsoft Standard XPS Microsoft Teams for Android Microsoft Trace Data Helper...

Key Judgements

Key Judgements are derived from validated ReportX claim identifiers rather than a second free-form model request. They may prioritize validation and collection, but they do not convert source-reported claims into confirmed customer impact.

Verified Facts

• CVE: CVE-2026-81963
• EPSS: 0.00631
• CISA KEV listed: True
• Source publisher: Tenable Blog
• Source published: 2026-09-08T18:07:55+00:00

Threat Classification

Report family: CISA KEV Alert. Exploitation state: Confirmed — CISA KEV listed. Remediation state: CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.. These labels come from the normalized report context and remain bounded by cited evidence.

Threat Severity Assessment

Severity is interpreted from structured scoring or source evidence when present. No customer-specific risk score, blast radius, or compromise state is inferred by this compiler.

Evidence & Source Assessment

Primary provenance is Tenable Blog. The compiler distinguishes source-reported material from independently structured NVD/CISA/EPSS evidence when those fields are actually present.

Timeline & Chronology

The normalized source publication timestamp is 2026-09-08T18:07:55+00:00. Additional intrusion, exploitation, disclosure, or remediation timestamps are not asserted unless they are present in the cited evidence body below.

Business Impact

Customer-specific business impact is not established by a public source record alone. Decision value comes from determining whether relevant assets, identities, dependencies, or services are actually present and exposed.

Enterprise Exposure Assessment

• Inventory and ownership teams should determine whether CVE-2026-81963 exists in the environment before assigning incident status.
• A positive exposure determination requires asset, version, identity, dependency, cloud/SaaS, or equivalent internal telemetry that can be tied to the cited condition.
• A negative determination should record the inventory evidence and timestamp used so the decision can be revalidated if the source record changes.

Technical Analysis

CVE‑2026‑81963 targets a flaw in the .NET runtime that allows arbitrary code execution when processing malicious input. The vulnerability is exploitable via crafted requests to services using the affected runtime. The patch mitigates the flaw by updating the runtime library and adding input validation. No additional mitigations are listed beyond patching.

• Affected product: Microsoft .NET runtime (all supported versions). • Weakness: Improper input validation leading to arbitrary code execution. • Root cause: Buffer overflow in the runtime’s handling of malformed data. • Prerequisites: Service running vulnerable .NET version, network exposure. • Reachable attack surface: Web applications, APIs, and background services. • Exploitability evidence: Confirmed exploitation in the wild (CISA KEV). • CVSS/CWE/EPSS: EPSS 0.00631; CVSS/CWE not provided. • Remediation: Apply Microsoft patch from September 2026 release. • Exposure: Systems with unpatched .NET runtime. • Post‑fix validation: Verify patch installation via version check and monitor for exploitation telemetry.

Report-Type Deep Dive

This CISA KEV Alert record is analyzed according to the evidence available for its family. Unsupported exploit chains, malware capabilities, breach scope, attribution, encryption, exfiltration, and regulatory consequences are intentionally not synthesized.

MITRE ATT&CK Assessment

Not established in cited evidence. ATT&CK technique mapping requires source-backed behavior. Any mappings present in the preserved analytical body are subject to the existing ReportX semantic gate; the compiler adds none of its own. The factory does not infer the missing fact from absence of evidence.

Indicators & Observables

Not established in cited evidence. Only source-derived, validated and safely defanged observables may be operationalized. The compiler does not invent domains, IP addresses, hashes, paths, process names, mutexes, or command lines. The factory does not infer the missing fact from absence of evidence.

Detection Engineering Guidance

Detection content remains evidence-conditioned. Production rules require source-backed behavior plus the telemetry needed to validate precision; otherwise the correct output is a telemetry specification rather than fabricated executable logic.

Detection Validation & Required Telemetry

• Identify the telemetry source and fields needed to observe the cited behavior before promoting detection logic.
• Replay or safely simulate only evidence-supported behavior, measure expected false positives, and retain test evidence with the rule version.
• Do not represent syntax validation as production efficacy; deployment requires environment-specific validation and accountable approval.

Threat Hunting Queries

Threat hunting should begin with exposure to CVE-2026-81963 and then pivot only on observables or behavior established in cited evidence. Absence of a source-backed pivot is an intelligence gap, not permission to invent one.

SOC Analyst Playbook

• Validate whether the affected technology, identity, dependency, service, or victim context exists internally.
• Preserve relevant logs and timestamps before destructive containment when an internal match is found.
• Escalate from intelligence validation to incident response only when internal telemetry or independently cited evidence supports the transition.

Incident Response & Containment Decision Plan

Public threat intelligence alone does not establish an internal incident. If internal evidence confirms relevance, preserve evidence, scope affected assets and identities, contain the validated path, eradicate the supported cause, recover, and verify recurrence controls.

Remediation & Validation Plan

• Remediation state from the normalized record: CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines..
• Apply vendor/CISA remediation only when that action is actually present in trusted evidence; otherwise obtain the authoritative remediation source before changing production systems.
• After change, verify asset/version state, exposure path, relevant telemetry, and rollback readiness rather than assuming the change succeeded.

Executive Decision Matrix

• No internal exposure evidence: retain as intelligence, document the negative exposure basis, and continue collection.
• Exposure confirmed but compromise unconfirmed: prioritize supported remediation and heightened telemetry while avoiding unsupported incident claims.
• Internal malicious activity confirmed: activate the organization's incident-response process using the preserved evidence and scoped telemetry.

Executive Recommendations

• Validate enterprise relevance to CVE-2026-81963 before treating the public record as a customer-specific finding.
• Prioritize evidence-backed remediation, telemetry coverage, and verification over severity labels alone.
• Keep unresolved exploitation, attribution, breach scope, and impact statements explicitly unresolved until corroborating evidence exists.

Intelligence Gaps & Collection Requirements

• Customer-specific exposure is not established by the public source record.
• Customer-specific compromise or impact is not established unless internal telemetry is supplied.
• Any source dimension not represented in the normalized evidence graph requires additional authoritative collection before it can drive a material claim.

Analytic Confidence & Limitations

Confidence is bounded by source reliability, information credibility, corroboration state, and unresolved contradictions already computed by ReportX. Structural compilation never raises epistemic confidence.

Forecast & Outlook

No new future event is predicted by the compiler. Forecast statements, when present in the preserved analytical body, must remain tied to ReportX supporting observation claims and explicit confidence rationale.

References

• Tenable Blog — https://www.tenable.com/blog/microsofts-september-2026-patch-tuesday-addresses-964-cves-cve-2026-81963-cve-2026-85880
• NIST National Vulnerability Database — https://nvd.nist.gov/vuln/detail/CVE-2026-81963
• CISA Known Exploited Vulnerabilities Catalog — https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• FIRST Exploit Prediction Scoring System — https://www.first.org/epss/