TL;DR: Apply Microsoft's vendor-supplied mitigations immediately in line with CISA BOD 26-04 guidance; if mitigations are unavailable, consider discontinuing use of the affected product until a fix is in place.
What Is CVE-2026-65660?
CVE-2026-65660 is a code injection vulnerability (CWE-94: Improper Control of Generation of Code) residing in Microsoft Office SharePoint. According to the National Vulnerability Database (NVD) and the CISA Known Exploited Vulnerabilities (KEV) catalog, the flaw stems from improper control over how the application generates or processes code, enabling an attacker to inject and execute malicious code over a network.
The vulnerability was published to NVD on 2026-08-11 and was added to the CISA KEV catalog on 2026-09-25, signaling confirmed exploitation activity that elevates it above a theoretical risk.
The CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H breaks down as follows:
- Attack Vector (AV:N): Exploitable remotely over the network — no physical or local access required.
- Attack Complexity (AC:L): Low complexity; no special conditions or race conditions are needed.
- Privileges Required (PR:L): The attacker needs only low-level (authenticated) privileges — a standard user account is sufficient.
- User Interaction (UI:N): No victim interaction is required; the attacker can act unilaterally.
- Scope (S:U): Impact is contained to the vulnerable component's security scope.
- Confidentiality / Integrity / Availability (C:H / I:H / A:H): All three impact dimensions are rated High, meaning a successful exploit can fully compromise data confidentiality, data integrity, and service availability.
Who and What Is Affected?
The affected product is Microsoft Office SharePoint, as identified by Microsoft and confirmed in both NVD and the CISA KEV catalog. Organizations that operate SharePoint — whether on-premises deployments or configurations that expose SharePoint services to the network — should treat this advisory as directly applicable to them.
Key exposure factors include:
- Internet-facing SharePoint instances: Any SharePoint environment accessible from the public internet is at elevated risk given the network-based attack vector.
- Intranet deployments: Even internally hosted SharePoint servers are at risk if an attacker gains a low-privilege foothold elsewhere on the network — the low complexity and low privilege requirement mean lateral movement scenarios are realistic.
- Shared and third-party hosted environments: Organizations using managed or hosted SharePoint services should verify with their provider that mitigations have been applied.
Because only low-level authenticated access is required, the attacker population is not limited to administrators or privileged users. Any valid SharePoint account — including contractor or partner accounts — could be leveraged.
Potential Impact
With CVSS impact sub-scores rated High across confidentiality, integrity, and availability, a successful exploitation of CVE-2026-65660 could allow an attacker to:
- Execute arbitrary code within the context of the SharePoint application, potentially at the privilege level of the service account running SharePoint.
- Access sensitive data stored in SharePoint libraries, lists, and document repositories — including files, metadata, and credentials that may be cached or accessible via SharePoint.
- Modify or destroy data within the SharePoint environment, impacting business records, compliance documentation, and collaborative workflows.
- Disrupt service availability, potentially causing SharePoint to become unavailable to legitimate users.
- Pivot to connected systems if the SharePoint service account or the compromised session has access to other internal resources, databases, or directory services.
CISA's inclusion of this CVE in the KEV catalog indicates that exploitation has been observed in the wild. Organizations should not treat this as a theoretical risk and should escalate it accordingly within their patch management and incident response workflows.
What to Do Now
The following actions are drawn directly from CISA's KEV required action guidance and vendor advisory direction. Prioritize these steps immediately:
- Apply vendor mitigations: Follow Microsoft's official advisory instructions for CVE-2026-65660. Apply all available patches or mitigations as directed. Refer to Microsoft's Security Update Guide for the specific update applicable to your SharePoint version and configuration.
- Comply with CISA BOD 26-04: Federal agencies and organizations subject to CISA's Binding Operational Directive 26-04 (Prioritizing Security Updates Based on Risk) must adhere to the patching timelines and prioritization criteria set out in that directive. CISA has identified specific forensics triage requirements associated with this vulnerability — review CISA's advisory for those details.
- Assess internet exposure: Identify all SharePoint instances in your environment and determine which are internet-facing. Prioritize those for immediate mitigation. Where internet exposure is not operationally required, restrict access at the network perimeter.
- Conduct forensic triage: Given active exploitation, consider whether your SharePoint environment may already be compromised. Review logs for unusual authentication events, unexpected code execution, or anomalous data access patterns. CISA's forensics triage requirements referenced in the KEV entry provide further guidance.
- Discontinue use if mitigations are unavailable: If your specific SharePoint configuration cannot be patched or mitigated, CISA's required action instructs organizations to follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product until mitigations are available.
- Review privileged and low-privilege accounts: Because only a low-privilege account is needed to exploit this flaw, audit which accounts have SharePoint access and enforce the principle of least privilege where possible.
Primary sources for remediation guidance:
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-65660
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Microsoft Security Update Guide: https://msrc.microsoft.com/update-guide/
How Continuous External Testing Surfaces This Exposure
One of the most reliable ways to know whether your SharePoint deployment is exposed to vulnerabilities like CVE-2026-65660 — before an attacker finds out — is through continuous external attack surface monitoring and vulnerability testing. Here is why this matters for a flaw of this profile:
- Internet-facing SharePoint is a high-value target: External testing enumerates your internet-facing assets, identifying SharePoint instances that may have been forgotten, misconfigured, or inadvertently exposed through cloud migrations or infrastructure changes.
- Patch validation, not just deployment: Applying a patch does not always mean the vulnerability is remediated. External testing validates from an attacker's perspective whether the fix is effective and whether no residual exposure remains — such as secondary SharePoint endpoints or staging environments running unpatched versions.
- Low-privilege attack paths are easy to miss internally: Because CVE-2026-65660 requires only a low-privilege account, internal patch audits that focus on privileged systems may underestimate the attack surface. External testing examines the network-reachable exposure without assumptions about internal privilege levels.
- Speed of detection matters when exploits are active: With CISA confirming exploitation in the wild, the window between vulnerability disclosure and successful attacks is narrow. Continuous testing — rather than periodic point-in-time assessments — reduces mean time to detect newly vulnerable or newly exposed assets.
- Prioritization across your environment: External testing results contextualize which of your assets are genuinely reachable from the internet and which CVEs on your patching backlog represent the most urgent real-world risk, helping security and operations teams focus limited resources effectively.
Sources & further reading: NVD CVE-2026-65660 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: msrc.microsoft.com, blog.previdian.com, cisa.gov. This advisory contains no exploit code.
Frequently asked questions
Does an attacker need administrator privileges to exploit CVE-2026-65660?
No. The CVSS vector for this vulnerability specifies Privileges Required: Low (PR:L), meaning a standard authenticated user account with low-level SharePoint access is sufficient. Administrative credentials are not required, which significantly broadens the potential attacker population.
Is CVE-2026-65660 being actively exploited?
Yes. CISA added CVE-2026-65660 to its Known Exploited Vulnerabilities (KEV) catalog on 2026-09-25, which indicates that exploitation has been observed in the wild. Organizations should treat this as an active threat requiring immediate remediation rather than a future risk.
What should I do if I cannot immediately apply Microsoft's mitigations?
CISA's required action guidance states that if mitigations are unavailable, organizations should follow applicable BOD 26-04 guidance for cloud services or discontinue use of the affected product. In the interim, consider restricting network access to your SharePoint environment, enforcing stricter access controls, and enhancing monitoring for suspicious activity while you work toward a full remediation.
Does this vulnerability affect SharePoint Online (Microsoft 365) or only on-premises SharePoint?
The verified facts available from NVD and CISA identify the affected product as Microsoft Office SharePoint without specifying a particular deployment model. Organizations should consult Microsoft's official Security Update Guide and advisory for CVE-2026-65660 to determine which specific SharePoint versions and deployment configurations are confirmed as affected.