CVE-2026-65660
validatedZero produced an exploit or a check.description
Microsoft SharePoint Server 2016, 2019, and Subscription Edition are affected by an improper code-generation control issue. An authorized attacker may perform spoofing over a network; the evidence does not provide additional preconditions.
mitigation
Update to SharePoint Enterprise Server 2016 16.0.5565.1001, SharePoint Server 2019 16.0.10417.20198, or SharePoint Server Subscription Edition 16.0.19725.20522, as applicable.
fixed in 16.0.5565.1001, 16.0.10417.20198, 16.0.19725.20522
outcome
Contextual check: a technique exists and was validated, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-08-11 17:04Zcve.org record for CVE-2026-65660
- 2026-09-24 00:00Z
- 2026-09-25cisa_kev: trigger signal, started the run
- 2026-09-25 00:00ZEUVD known exploited (ENISA)
- 2026-09-25 00:00ZCISA Known Exploited Vulnerabilities catalog
- 2026-09-29 20:42ZShadowForge-Cyber/CVE-2026-65660-Poc
- 2026-10-02 00:27ZSharePoint RCE and MikroTik RouterOS Flaws Actively Exploited in the Wild
this entry in the feed
GET /api/v1/feed/CVE-2026-65660
{ "etk_id": "ETK-2026-9", "cve_id": "CVE-2026-65660", "display_id": "CVE-2026-65660", "ghsa_id": null, "euvd_id": "EUVD-2026-56431", "status": "published", "anchor_state": "anchored", "title": "Authorized code injection in Microsoft SharePoint", "summary": "Microsoft SharePoint Server 2016, 2019, and Subscription Edition are affected by an improper code-generation control issue. An authorized attacker may perform spoofing over a network; the evidence does not provide additional preconditions.", "mitigation": "Update to SharePoint Enterprise Server 2016 16.0.5565.1001, SharePoint Server 2019 16.0.10417.20198, or SharePoint Server Subscription Edition 16.0.19725.20522, as applicable.", "vendor": "Microsoft", "product": "SharePoint", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 16.0.0, < 16.0.5565.1001" ], "ecosystem": null, "fixed_versions": [ "16.0.5565.1001" ], "package_name": "Microsoft SharePoint Enterprise Server 2016", "purl": null }, { "affected_notes": [], "affected_ranges": [ ">= 16.0.0, < 16.0.10417.20198" ], "ecosystem": null, "fixed_versions": [ "16.0.10417.20198" ], "package_name": "Microsoft SharePoint Server 2019", "purl": null }, { "affected_notes": [], "affected_ranges": [ ">= 16.0.0, < 16.0.19725.20522" ], "ecosystem": null, "fixed_versions": [ "16.0.19725.20522" ], "package_name": "Microsoft SharePoint Server Subscription Edition", "purl": null } ], "cwes": [ 94 ], "cvss_score": 8.8, "cvss_src": "nvd", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "epss_score": 0.021, "epss_percentile": 0.8154, "epss_asof": "2026-10-21", "automation": "contextual", "check": true, "check_confidence_basis": "assessed", "exploit": false, "pipeline_minutes": 28.9282187, "t0_at": "2026-08-11T17:04:55.666000+00:00", "signals": { "check": { "at": "2026-10-02T01:40:14.720418+00:00", "days": 51.35785942613426, "is_lower_bound": false, "measured_at": "2026-08-11T17:04:55.666000+00:00", "url": null }, "kev": { "at": "2026-09-24T00:00:00+00:00", "days": 44, "is_lower_bound": false, "measured_at": "2026-08-11T17:04:55.666000+00:00", "precision": "day", "url": "https://vulncheck.com/cve/CVE-2026-65660" }, "public_poc": { "at": "2026-09-25T20:27:27+00:00", "days": 45.14064043981482, "is_lower_bound": false, "measured_at": "2026-08-11T17:04:55.666000+00:00", "url": "https://github.com/ShadowForge-Cyber/CVE-2026-65660-Poc" }, "trigger_signal": { "at": "2026-09-25T00:00:00+00:00", "days": 44.288244606481484, "is_lower_bound": false, "measured_at": "2026-08-11T17:04:55.666000+00:00", "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2026-65660" } } }
published 2026-09-29 20:19Z
last change 2026-10-21 20:58Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.