KEV Lag Tracker → CVE-2026-65660. Data verified against the official CISA KEV catalog and the National Vulnerability Database.

CISA added CVE-2026-65660 (Microsoft SharePoint) to the Known Exploited Vulnerabilities catalog on September 25, 2026. It was publicly known for 45 days before CISA confirmed active exploitation. A KEV listing is CISA’s official confirmation that a vulnerability is being exploited in the wild.

The Record

CVECVE-2026-65660
Vendor / productMicrosoft SharePoint
VulnerabilityMicrosoft SharePoint Code Injection Vulnerability
CVSS base score8.8
EPSS probability the day before the KEV listing1.19% (66.6% percentile)
NVD publication dateAugust 11, 2026
Added to CISA KEVSeptember 25, 2026
Lag (public → KEV listing)45 days
Federal patch deadlineSeptember 28, 2026
Known ransomware useNo

Measured against the 1739 entries in our tracker with verified publication dates, CVE-2026-65660 was flagged faster than 65% of them.

What CISA Reported

CISA describes the flaw as follows: “Microsoft SharePoint contains a code injection vulnerability which could allow an authorized attacker to execute code over a network.”

Federal Patch Deadline

Under Binding Operational Directive rules, U.S. federal agencies must remediate CVE-2026-65660 by September 28, 2026 — a 3-day remediation window from the KEV listing date. Private organizations are not bound by that deadline; CISA treats it as the benchmark for how urgently a confirmed-exploited flaw should be patched.

What EPSS Forecast Before the Confirmation

The EPSS forecast (FIRST’s daily estimate of the probability a CVE will be exploited within 30 days) put CVE-2026-65660 at 1.19% on the day before CISA confirmed active exploitation — the 66.6% percentile of all scored CVEs that day. That places it outside the top 10% of EPSS risk on the eve of confirmation — a patch queue ordered by EPSS alone would have left it for later.

EPSS for CVE-2026-65660Value
Probability the day before the KEV listing1.19%
Percentile the day before the KEV listing66.6%
Probability today (October 9, 2026)2.10%
Percentile today81.2%

Today’s figure is not evidence that the forecast worked: EPSS reacts to the KEV listing itself, so the score for any confirmed-exploited CVE tends to rise after CISA acts. Only the eve-of-listing number was available to a defender making the call. Across every KEV entry we track, we measured how often that number was high — see the EPSS accuracy analysis.

How This Compares to Microsoft’s Track Record

At 45 days, CVE-2026-65660 was flagged faster than Microsoft’s 531-day median across the 389 of its KEV entries with verified publication dates. Microsoft currently ranks #20 on our KEV Lag leaderboard.

Microsoft in the CISA KEV catalogValue
Tracked KEV entries389
Median lag (public → KEV listing)531 days
0-day rate (exploited at or before disclosure)23%
Entries tied to known ransomware campaigns104

Other Recent Microsoft KEV Additions

CVEProductAdded to KEVLag (days)Ransomware
CVE-2026-81963WindowsSeptember 8, 20260No
CVE-2026-85880WindowsSeptember 8, 20260No
CVE-2019-1068SQL ServerAugust 26, 20262599No
CVE-2026-33824Internet Key Exchange (IKE) Service ExtensionsAugust 18, 2026126No
CVE-2026-55040SharePointAugust 18, 202635No

Frequently Asked Questions

What is CVE-2026-65660?

CVE-2026-65660 is a vulnerability in Microsoft SharePoint (Microsoft SharePoint Code Injection Vulnerability) that CISA added to its Known Exploited Vulnerabilities catalog on September 25, 2026. A KEV listing is CISA’s official confirmation that the flaw is being exploited in the wild.

How long was CVE-2026-65660 public before CISA confirmed exploitation?

45 calendar days, measured from its NVD publication date to the date CISA added it to the KEV catalog.

What is the federal patch deadline for CVE-2026-65660?

U.S. federal agencies must remediate CVE-2026-65660 by September 28, 2026, a 3-day window from the KEV listing date. Private organizations are not bound by that deadline, but CISA treats it as the benchmark for how urgently a confirmed-exploited flaw should be patched.

Is CVE-2026-65660 used in ransomware campaigns?

CISA has not flagged CVE-2026-65660 as known to be used in ransomware campaigns. That field reflects confirmed campaign use, not the absence of risk.

What was the EPSS score for CVE-2026-65660 before it was confirmed as exploited?

1.19% — the probability EPSS assigned on the day before CISA added CVE-2026-65660 to the KEV catalog, placing it in the 66.6% percentile of all scored CVEs that day. That is outside the top 10% of EPSS risk. Its score today is higher in most cases because EPSS reacts to the KEV listing itself, so only the eve-of-listing figure reflects what a defender could have acted on.

How does this compare to other Microsoft vulnerabilities?

Across 389 Microsoft entries with verified publication dates, the median lag is 531 days and 23% were exploited at or before disclosure. CVE-2026-65660, at 45 days, is faster than that median.

Related Coverage

Primary Sources

How We Track This

This page is generated from our CISA KEV Lag Tracker, which syncs the official CISA KEV catalog daily and records the date each CVE is added. For every entry we retrieve the original NVD publication date and compute the lag in calendar days. No date or figure on this page is estimated or taken from a third-party source — they come directly from CISA and NVD records. Free to cite with attribution to CVEDaily (CC BY 4.0).