dbcve.org
Sharepoint ServerApplication · Microsoft

CVE-2026-20958

MEDIUM · 5.4 CVSS v3.1 Published 2026-01-13
Fix available
A fix is available. Upgrade to 16.0.19127.20442 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Server-side request forgery (ssrf) in Microsoft Office SharePoint allows an authorized attacker to disclose information over a network.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Server-side request forgery (SSRF) vulnerability in Microsoft Office SharePoint enables an authenticated attacker to cause the SharePoint server to make arbitrary network requests to internal or external resources, potentially exposing sensitive information from the server or connected internal systems.

MitigationApply Microsoft security updates for SharePoint Server to address the SSRF vulnerability. Restrict SharePoint server network access to necessary endpoints and implement network segmentation to limit exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sharepoint ServerApplication
Affected:< 16.0.19127.20442= 2016= 2019

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if SharePoint Server is installed
    Check for SharePoint services in Windows Services (e.g., 'SharePoint Timer Service', 'SharePoint Administration') or look for SharePoint Central Administration website on port 443/80
    Affected if No SharePoint Server services or sites found means not affected
  2. Determine the installed SharePoint version build number
    Run PowerShell as Administrator: (Get-SPFarm).BuildVersion or check registry at HKLM\SOFTWARE\Microsoft\Shared Tools\web server extensions\16.0\SharePoint\Setup\Version for SP2016/2019
    Affected if Build version lower than 16.0.19127.20442 indicates a vulnerable version
  3. Confirm the specific SharePoint edition
    Run PowerShell: Get-SPServer -Identity $env:COMPUTER | Select-Object -Property Version, Build, Edition or check Central Administration > System Settings > Manage servers in farm
    Affected if Running SharePoint Server 2016 or 2019 (any build) is affected, as these are explicitly listed in the vulnerable versions

You are affected if SharePoint Server is installed and the build version is below 16.0.19127.20442, or if you are running SharePoint Server 2016 or 2019 at any version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 16.0.19127.20442 or later
Fixed in 16.0.19127.20442
Interim mitigation

Apply Microsoft security updates for SharePoint Server to address the SSRF vulnerability. Restrict SharePoint server network access to necessary endpoints and implement network segmentation to limit exposure.

Recommended fix Moderate confidence

SharePoint Server 2019: Apply March 2026 Security Update (KB5002763) to reach version 16.0.19127.20442 or later; SharePoint Server 2016: Apply March 2026 Security Update; SharePoint Server Subscription Edition: Apply March 2026 Security Update to reach version 16.0.19127.20442 or later

  1. Identify the current SharePoint Server version by checking Central Administration > System Settings > Manage farm servers
  2. For SharePoint Server 2019: Apply security update KB5002763 (released March 2026) which contains the fix for this SSRF vulnerability
  3. For SharePoint Server 2016: Apply the corresponding March 2026 security update for SharePoint Server 2016
  4. After applying the update, verify the version matches or exceeds 16.0.19127.20442 using: Get-SPProduct -LocalServer | Select-Object -Property Version
  5. Run SharePoint Products Configuration Wizard (PSCONFIG) to complete the update
  6. Confirm the vulnerability is resolved by reviewing the patched version in Central Administration
Caveat Standard SharePoint security update - minimal risk; may require farm downtime for update installation and PSConfig execution; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sharepoint Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-20958 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-20958 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data