CVE-2026-65660

CRITICALPre-NVD 8.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than the CVSS score beside it.

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-09-25), indicating real-world exploitation has been confirmed by US federal agencies. It is also listed on ENISA's EU Known Exploited Vulnerabilities catalogue (Source: ENISA EUVD). The CNA's CVSS baseline 8.8 retained for reference (NVD's own analysis pending). The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 8.8 HIGH under the CNA's CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, the CNA's CVSS, EPSS, ENISA's EU Known Exploited Vulnerabilities catalogue, GitHub Security Advisory
Trending — 4 sources updated this weekExploited in the wild

Also known asEUVD-2026-56431 (ENISA EUVD) · GHSA-r94x-x846-rxqx (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedENISA EU KEV: Listed (Source: ENISA EUVD)EPSS PROB: 8.2%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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

CVSS v3
8.8
EG Score
9.0CRITICALhigh confidence
EG Risk
80
EG Risk 80/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
8.2%
EPSS %ILE
94th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 8.8 HIGH.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.the CNA's CVSS · CVSS v3.0 or v3.1
EG Likelihood
8.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and ENISA EU KEV (Source: ENISA EUVD) and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

ENISA EU KEV: listed September 25, 2026, reported by CSIRT-IE.

Source: ENISA EUVD (EU Known Exploited Vulnerabilities catalogue), reproduced with acknowledgement. How a listing moves the EG score

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

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.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-65660 · https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk · https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk · https://nvd.nist.gov/vuln/detail/CVE-2026-65660

Published

August 11, 2026

Last Modified

October 30, 2026

Advisory Details (3)

Auto-updated Oct 30, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: microsoft, cisa.
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-65660
Web page

CVE-2026-65660: Previdian observes two-stage SharePoint exploitation attempts

https://blog.previdian.com/cve-2026-65660-previdian-observes-two-stage-sharepoint-exploitation-attempts/
Microsoft

Security Update Guide - Microsoft Security Response Center

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-65660

Vendor Advisories for CVE-2026-65660(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 33× in last 7d / 219× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 664 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 564 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 10:39 UTCEG score recompute
  2. 2026-11-02 10:39 UTCVendor advisory
  3. 2026-11-02 10:39 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub severity MODERATE · GitHub CVSS 6.5
  4. 2026-11-01 16:35 UTCEPSS rescoreEPSS 8.2% · 94th percentile
  5. 2026-11-01 12:56 UTCEG score recompute
  6. 2026-11-01 12:56 UTCVendor advisory
  7. 2026-11-01 12:56 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub severity MODERATE · GitHub CVSS 6.5
  8. 2026-10-31 16:33 UTCEPSS rescoreEPSS 8.2% · 94th percentile
  9. 2026-10-31 15:14 UTCVendor advisory
  10. 2026-10-31 15:13 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  11. 2026-10-30 17:31 UTCEG score recompute
  12. 2026-10-30 17:31 UTCVendor advisory
  13. 2026-10-30 17:31 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  14. 2026-10-30 16:35 UTCEPSS rescoreEPSS 8.2% · 94th percentile
  15. 2026-10-30 15:37 UTCVendor advisory
  16. 2026-10-30 15:37 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  17. 2026-10-29 17:55 UTCEG score recompute
  18. 2026-10-29 17:55 UTCVendor advisory
  19. 2026-10-29 17:54 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  20. 2026-10-29 16:33 UTCEPSS rescoreEPSS 8.2% · 94th percentile
  21. 2026-10-28 20:10 UTCEG score recompute
  22. 2026-10-28 20:10 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  23. 2026-10-28 16:33 UTCEPSS rescoreEPSS 8.2% · 94th percentile
  24. 2026-10-28 08:52 UTCEG score recompute
  25. 2026-10-28 08:52 UTCVendor advisory
Show 75 more
  1. 2026-10-28 08:51 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  2. 2026-10-27 16:32 UTCEPSS rescoreEPSS 8.2% · 94th percentile
  3. 2026-10-27 11:09 UTCEG score recompute
  4. 2026-10-27 11:09 UTCVendor advisory
  5. 2026-10-27 11:09 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  6. 2026-10-26 16:32 UTCEPSS rescoreEPSS 8.2% · 94th percentile
  7. 2026-10-26 13:27 UTCEG score recompute
  8. 2026-10-26 13:26 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  9. 2026-10-26 11:29 UTCEG score recompute
  10. 2026-10-25 16:33 UTCEPSS rescoreEPSS 8.2% · 94th percentile
  11. 2026-10-25 13:47 UTCEG score recompute
  12. 2026-10-25 13:47 UTCVendor advisory
  13. 2026-10-25 13:47 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  14. 2026-10-25 13:46 UTCENISA EU KEV listingEUVD-2026-56431 · listed September 25, 2026 · reported by CSIRT-IE · Source: ENISA EUVD
  15. 2026-10-25 11:48 UTCEG score recompute
  16. 2026-10-25 11:48 UTCVendor advisory
  17. 2026-10-25 11:48 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  18. 2026-10-24 16:33 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  19. 2026-10-24 14:06 UTCEG score recompute
  20. 2026-10-24 14:06 UTCVendor advisory
  21. 2026-10-24 14:06 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  22. 2026-10-23 16:32 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  23. 2026-10-23 16:22 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  24. 2026-10-22 18:40 UTCEG score recompute
  25. 2026-10-22 18:40 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  26. 2026-10-22 16:35 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  27. 2026-10-21 20:57 UTCEG score recompute
  28. 2026-10-21 20:57 UTCVendor advisory
  29. 2026-10-21 20:57 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  30. 2026-10-21 16:33 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  31. 2026-10-21 07:04 UTCEG score recompute
  32. 2026-10-21 07:04 UTCVendor advisory
  33. 2026-10-21 07:04 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  34. 2026-10-20 16:33 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  35. 2026-10-20 09:19 UTCEG score recompute
  36. 2026-10-20 09:19 UTCVendor advisory
  37. 2026-10-20 09:19 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  38. 2026-10-19 16:32 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  39. 2026-10-19 11:36 UTCEG score recompute
  40. 2026-10-19 11:36 UTCVendor advisory
  41. 2026-10-19 11:36 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  42. 2026-10-18 16:32 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  43. 2026-10-18 13:53 UTCVendor advisory
  44. 2026-10-18 13:53 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  45. 2026-10-18 03:21 UTCEG score recompute
  46. 2026-10-17 16:35 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  47. 2026-10-17 16:09 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  48. 2026-10-16 18:27 UTCEG score recompute
  49. 2026-10-16 18:26 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  50. 2026-10-16 16:43 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  51. 2026-10-15 20:41 UTCEG score recompute
  52. 2026-10-15 20:41 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  53. 2026-10-15 16:32 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  54. 2026-10-14 22:58 UTCEG score recompute
  55. 2026-10-14 22:58 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  56. 2026-10-14 16:33 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  57. 2026-10-14 01:13 UTCEG score recompute
  58. 2026-10-14 01:13 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  59. 2026-10-13 16:34 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  60. 2026-10-13 03:30 UTCEG score recompute
  61. 2026-10-13 03:30 UTCVendor advisory
  62. 2026-10-13 03:30 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  63. 2026-10-12 16:34 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  64. 2026-10-12 15:46 UTCEG score recompute
  65. 2026-10-12 05:46 UTCVendor advisory
  66. 2026-10-12 05:45 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  67. 2026-10-12 01:54 UTCVendor advisory
  68. 2026-10-12 01:54 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  69. 2026-10-11 22:07 UTCVendor advisory
  70. 2026-10-11 22:07 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  71. 2026-10-11 19:31 UTCEG score recompute
  72. 2026-10-11 18:18 UTCVendor advisory
  73. 2026-10-11 18:18 UTCGHSA enrichmentGHSA-r94x-x846-rxqx · GitHub CVSS 6.5
  74. 2026-10-11 16:47 UTCEG score recompute
  75. 2026-10-11 14:31 UTCVendor advisory

Frequently asked(6)

What is CVE-2026-65660?
CVE-2026-65660 is a critical-severity vulnerability; its CVE record was published on August 11, 2026. Improper control of generation of code ('code injection') in Microsoft Office SharePoint allows an authorized attacker to execute code over a network.
When was CVE-2026-65660 made public?
CVE-2026-65660 was made public on August 11, 2026: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on August 11, 2026. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
Is CVE-2026-65660 actively exploited?
Yes. CISA added CVE-2026-65660 to the Known Exploited Vulnerabilities catalog on September 25, 2026, affecting Microsoft SharePoint. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it. ENISA's EU Known Exploited Vulnerabilities catalogue lists CVE-2026-65660 (added September 25, 2026, reported by CSIRT-IE): ENISA records its exploitation in the wild. Source: ENISA EUVD (EU Known Exploited Vulnerabilities catalogue), reproduced with acknowledgement.
What is the CVSS score of CVE-2026-65660?
CVE-2026-65660 has a CVSS base score of 8.8 (the CNA's own assessment, by microsoft; NVD's own analysis pending). EchelonGraph synthesises the CNA's CVSS + CISA KEV + ENISA's EU KEV (Source: ENISA EUVD) + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2026-65660?
CVE-2026-65660 affects Microsoft SharePoint.
How do I remediate CVE-2026-65660?
A fix for CVE-2026-65660 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-65660 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-65660

Explore →

Is Your Infrastructure Affected by CVE-2026-65660?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.