SecOps SignalSecurity Intelligence Workspace
Collection Degraded30 / 46 Sources HealthyPublic Intel Only
Vulnerabilities/CVE-2026-65660Public Intelligence Dossier
Source: Microsoft · Limited verification•Last verified: •Collection Degraded
CVE-2026-65660ListedImportant (raw)CVSS 8.8

Microsoft SharePoint Server Remote Code Execution Vulnerability

Published: 11 Aug 2026•Last updated: 25 Sept 2026, 12:30 PM IST•Source identifier: Unknown
Dossier completeness: source-provided sections 3 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Listed
Added25 Sept 2026
Due28 Sept 2026
RansomwareUnknown
CVSS score
8.8Important (raw)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Metric sourceMicrosoft MSRC CVRF
EPSS probability
2.1%0.021
Percentile81st
Weakness type
—
No further CWE recorded
Remediation
Patch status unknown
KB5002905, KB5002906, KB5002894, KB5002896, KB5002893

Why It Matters

Analysis dossier

Why It Matters

Improper control of generation of code ('code injection') in Microsoft Office SharePoint allows an authorized attacker to execute code over a network.

SOC priority

Immediate Attention

Actively exploited

Yes

Publicly disclosed

Unknown

Risk basis: Known exploitation signal from CISA KEV or ransomware metadata

Affected Products & Remediation

3 source-backed products
Affected products and versions (source)
  • Microsoft SharePoint Enterprise Server 2016 · version range not provided by source · Microsoft MSRC · Source
  • Microsoft SharePoint Server 2019 · version range not provided by source · Microsoft MSRC · Source
  • Microsoft SharePoint Server Subscription Edition · version range not provided by source · Microsoft MSRC · Source
Recorded patch / KBKB5002905, KB5002906, KB5002894, KB5002896, KB5002893

Vendor or catalog guidance (source)

  • Microsoft MSRC: Install the security update KB5002905 listed by MSRC
  • Microsoft MSRC: Install the security update KB5002906 listed by MSRC
  • Microsoft MSRC: Install the security update KB5002894 listed by MSRC
  • Microsoft MSRC: Install the security update KB5002896 listed by MSRC
  • Microsoft MSRC: Install the security update KB5002893 listed by MSRC

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Listed
Exploited (source statement)
Yes
Publicly disclosed (source)
Unknown

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.

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched kev-network-exposure (CVSS AV:N, CISA KEV Listed); microsoft-enterprise (Affected product: Microsoft SharePoint Enterprise Server 2016, Vendor: Microsoft)

Exposure

  1. Identify assets with the exact CVE and confirm the affected product/version against the advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · KEV listing raises urgency, but inventory is needed to establish local exposure. · Rule kev-network-exposure
  2. Identify affected Microsoft products and compare local builds with the MSRC advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · The MSRC product/build mapping establishes applicability. · Rule microsoft-enterprise

Exploitation evidence

  1. Review relevant edge or application access logs for unusual requests around the advisory window.Telemetry: CommonSecurityLog · Log review is a hunting hypothesis; KEV listing alone does not show local exploitation. · Rule kev-network-exposure
Show more (2)

Exploitation evidence

  1. Review the advisory's documented behavior on matching hosts before selecting a hunt.Telemetry: DeviceProcessEvents · Product family alone does not justify a CVE-specific detection. · Rule microsoft-enterprise

Response

  1. Recheck the affected assets after the source-stated mitigation or update is applied.Telemetry: DeviceTvmSoftwareVulnerabilities · A follow-up inventory check verifies local remediation. · Rule kev-network-exposure

CISA KEV Record

Catalog entry
25 Sept 2026
Required action due
28 Sept 2026
Known ransomware use
Unknown

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.

Change History & Source Data

— No recorded material change

CNA / source
Unknown
Record status · verification
UPDATED · Microsoft primary source linked; CISA KEV confirmed
CPE
Unknown

Linked by the query's stored exact CVE association. Review required tables and validation status before use.

Detection Hunting Query
Target: DeviceTvmSoftwareVulnerabilities•Defender XDR
Detect endpoints exposed to CVE-2026-65660
Purpose: Exposure assessment (Category: Exposure Check)Why linked: Query metadata names CVE-2026-65660
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2026-65660"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc
Schema Checked · Not runtime validatedSource: SecOps Signal deterministic template · Limited verificationStatic screening: Passed structure and schema checks; tenant execution is not verified.
SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.