Microsoft · Parser conflict
Microsoft SharePoint Unsafe Deserialisation Vulnerability
At a glance
Actively exploited in the wild — prioritise confirming exposure.
Medium rather than High: exposure is scored at a default because we cannot see your systems or suppliers. If you run or depend on Microsoft SharePoint Server, treat it as High.
Briefing
There is no written leader briefing for this story yet. These questions come from the facts we hold.
Questions to ask IT
- Do we run Microsoft SharePoint Server, and which versions?
- Is any of it reachable from the internet?
- Have we checked whether it has already been used against us?
- If it is not yet patched, what mitigation is in place, and will the fix be done by 12 Nov?
Next steps
- Confirm exposure and remediation status for affected products
Vulnerability facts
Full CVE detail CVE-2026-20963- 9.8 · CriticalExploitable over the network without any account, and no one has to click or open anything. High impact on confidentiality, integrity and availability.CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Listed: attacks using it have been seen (on the catalogue since )
- Elevated attack likelihood (~29.2% in 30 days)
No technical write-up beyond these facts and the summary below yet.
Next steps
- Confirm whether affected products/versions are present and prioritise patching or mitigations
Summary
- Microsoft SharePoint contains a deserialisation of untrusted data vulnerability that allows an unauthorised attacker to execute code over a network.
- CVE-2026-20963 has an estimated attack likelihood score of 0.296 (~29.6% estimated chance of exploitation in the next 30 days; 98.1th percentile) as of 2026-09-24. This is a probability signal from FIRST, not confirmed exploitation.
- CVE-2026-20963 is confirmed as exploited in the wild (US known-exploited catalogue)
- Authoritative catalogues report active exploitation of this vulnerability.
Products and services involved
- Microsoft SharePoint Server93% match confidence · CVE-2026-20963
Same event, different frames
Distinct often headline the same incident differently.
Pulse
Last checked 23m ago · Next recheck 10 Nov 2026, 12:39 UK time · 3 quiet checks collapsed
in the next 30 days first recorded at 29.2% (elevated likelihood signal, not confirmed exploitation).
Elevated — confirm exposure; this is a probability signal, not confirmed exploitation.
2 quiet checks hidden.
Sources
Microsoft SharePoint Deserialization of Untrusted Data Vulnerability
CVE-2026-20963: elevated exploitation probability
How we know
Statements extracted from sources. Higher confidence means stronger corroboration.
- ClaimedHeadline60% confidence
Microsoft SharePoint Deserialization of Untrusted Data Vulnerability
- ProbableSummary fact75% confidence
CVE-2026-20963 has an estimated attack likelihood score of 0.296 (~29.6% estimated chance of exploitation in the next 30 days; 98.1th percentile) as of 2026-09-24. This is a probability signal from FIRST, not confirmed exploitation.
- ConfirmedCVE identifier95% confidence
Event involves CVE-2026-20963
- ConfirmedKnown-exploited catalogue98% confidence
CVE-2026-20963 is confirmed as exploited in the wild (US known-exploited catalogue)

