Skip to content
major vulnerability· requires attention

Affects Microsoft Office SharePoint, a widely used enterprise product; SSRF enabling privilege escalation could impact many organizations.

Web

CVE-2026-70326

HIGH
High
EPSS 0.59%Patch availableAug 12, 2026

Authenticated SSRF in SharePoint enabling internal network access and privilege escalation.

common questions

Is CVE-2026-70326 being exploited?

Not confirmed. CVE-2026-70326 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.59% probability of exploitation in the next 30 days.

How severe is CVE-2026-70326?

CVE-2026-70326 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-70326?

Yes. A fix has been recorded for CVE-2026-70326. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-70326 affect?

CVE-2026-70326 affects Microsoft Office SharePoint. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-70326?

Apply vendor patch/mitigations when available, restrict SharePoint access, segment network, monitor logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Microsoft Office SharePoint
impact

Authenticated server-side request forgery allows access to internal resources and elevation of privileges on SharePoint and connected services.

action required

Immediate action required

affected versions
Microsoft Microsoft SharePoint Server Subscription Edition
  • affected>= 16.0.0 and < 16.0.19725.20522

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free