Patch tracker / CVE reference / CVE-2026-35439

CVE-2026-35439

CVE-2026-35439 is a high severity Microsoft vulnerability with a CVSS score of 8.8. Microsoft has shipped the fix: deploy one of the 3 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

High

8.8

CVSS

9.1%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 9.1%. CVSS 8.8 (High).

This CVE is among the lower half of tracked Microsoft CVEs by EPSS exploit probability.

Senserva AI Opinion for CVE-2026-35439

This is a remote code execution flaw in on-premises SharePoint, affecting Enterprise Server 2016, Server 2019, and Subscription Edition, and at CVSS 8.8 it is authenticated-adjacent rather than pure unauthenticated. It is not in CISA KEV and EPSS sits at 3 percent, so there is no confirmed exploitation yet, but SharePoint RCE bugs have historically drawn attacker attention once patches are reverse engineered. Anyone still running these on-prem farms, rather than SharePoint Online, is exposed.

Do this: Apply Microsoft's patch to all SharePoint 2016, 2019, and Subscription Edition servers and confirm the web and application tiers are all updated.

AI-generated from public data, 2026-07-23. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-35439

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I am an IT admin assessing a vulnerability. Facts for CVE-2026-35439 (source: https://senserva.com/cve/CVE-2026-35439.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2026-35439: High severity Microsoft vulnerability, CVSS 8.8
- EPSS 30-day exploitation probability: 9.1%
- Actively exploited (CISA KEV): no
- Fixed by: KB5002863, KB5002868, KB5002870
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) What to patch or mitigate first. 4) How to check whether my devices are exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Schedule normally

No exploitation observed: not in the CISA KEV catalog, EPSS 9%.

Fixed by KB5002863 and 2 more (by build, listed below). Download from the Microsoft Update Catalog, or deploy via Windows Update, Intune, or WSUS.

Do this now: Deploy with your normal update cycle. This page refreshes daily; the verdict changes the day the data does.

Official patch(es) for CVE-2026-35439

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5002863, KB5002868, KB5002870 are installed across the affected products. Senserva does this automatically across your tenant and flags every missing patch.

Apply the Microsoft security updates below to fix CVE-2026-35439. Each KB page carries the Microsoft Update Catalog download, Microsoft's known issues for the update, a copy-paste PowerShell check for whether it is installed, and the Senserva AI read.

KB5002863 KB5002868 KB5002870

Scope and sources

Affected products

Fixed by the same updates

CVE-2026-45659 CVE-2026-33110 CVE-2026-33112 CVE-2026-40357 CVE-2026-40365 CVE-2026-40367 CVE-2026-40368 CVE-2026-47294

Authoritative references

Official CVE record (cve.org)NVD detail Microsoft MSRC FIRST.org EPSS

Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.