CVE-2026-65660
Exploitation confirmed. First attested on 2026-09-24 by CISA-ADP, CISA KEV, GCVE · enisa-cnw-kev, GCVE · previdian.
- Published2026-08-11
- Fixed in16.0.19725.20522
- WeaknessCWE-94
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Improper control of generation of code ('code injection') in Microsoft Office SharePoint allows an authorized attacker to execute code over a network.
Timeline
dates in UTCVersions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 16.0 | < 16.0.19725.20522 | 16.0.19725.20522 | NVD |
| 2016.x | = 2016 | no fix published | NVD |
| 2019.x | = 2019 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA3 products
As microsoft, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- Microsoft SharePoint Enterprise Server 2016
platforms: x64-based Systems
Affected- ≥ 16.0.0, < 16.0.5565.1001fixed in 16.0.5565.1001custom
- Microsoft SharePoint Server 2019
platforms: x64-based Systems
Affected- ≥ 16.0.0, < 16.0.10417.20198fixed in 16.0.10417.20198custom
- Microsoft SharePoint Server Subscription Edition
platforms: x64-based Systems
Affected- ≥ 16.0.0, < 16.0.19725.20522fixed in 16.0.19725.20522custom
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-10-30
Fix
- Update Microsoft sharepoint server to 16.0.19725.20522
- CISA’s 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.due 2026-09-28
Advisories and patches
- msrc.microsoft.comPatch · Vendor Advisory
Detection
read 2026-11-06 06:14 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHub1 repository, unverifiedknown since 2026-11-06HORKimhab/CVE-2026-65660
- Metasploit modules
- none listed Metasploit Framework
CISA Known Exploited Vulnerability
- Date Added
- 2026-09-25
- Patch Due Date
- 2026-09-28
- Ransomware Use
- Unknown
- 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.
Sources
- NVDCVE recordread 2026-10-26
- CISA KEVKEV entry2026-09-25
- ENISA EUVDexploitation2026-09-252026-09-25
- GCVEexploitation2026-09-24
- CISA-ADPSSVC decisionactive2026-09-25
- CNACVSS 3.18.8known since 2026-10-26
- CNAweakness (CWE)CWE-94known since 2026-10-26
- FIRST EPSSEPSS score9.9 %2026-11-08
- PoC-in-GitHubproof of concept1known since 2026-11-06
- GitHub Advisoriesadvisory—
Identifiers
- EUVD-2026-56431same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-r94x-x846-rxqxsame flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2026-08-11
- Last Modified
- 2026-10-26
- NVD status
- Analyzed
- GitHub Advisory
- GHSA-r94x-x846-rxqx
Frequently asked questions
What is CVE-2026-65660?
Is CVE-2026-65660 actively exploited?
What is the CVSS score for CVE-2026-65660?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- For a threat intelligence platform: malware, C2 and ransomware indicators over STIX/TAXII.
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CISA KEV · CC0-1.0 (cisagov/kev-data)
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GCVE · GCVE dump terms (preserve source attribution)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-r94x-x846-rxqx
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- PoC-in-GitHub · CC0-1.0
- CISA Vulnrichment · CC0-1.0