dbcve.org
Sharepoint ServerApplication · Microsoft

CVE-2026-62826

MEDIUM · 5.4 CVSS v3.1 Developing Published 2026-07-16
Fix available
A fix is available. Upgrade to 16.0.19725.20434 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable 5 weeks old

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
Improper neutralization of input during web page generation ('cross-site scripting') in Microsoft Office SharePoint allows an authorized attacker to perform spoofing 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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-07-30.

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.19725.20434= 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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.19725.20434 or later
Fixed in 16.0.19725.20434
Recommended fix Moderate confidence

SharePoint Server 2019/2016 with build 16.0.19725.20434 or later (September 2024 Cumulative Update)

  1. 1. Identify the current SharePoint Server build version by navigating to SharePoint Central Administration > System Settings > Manage farm servers
  2. 2. For SharePoint Server 2019: Install the September 2024 or later Cumulative Update (CU) that includes build 16.0.19725.20434
  3. 3. For SharePoint Server 2016: Install the September 2024 or later Cumulative Update that includes build 16.0.19725.20434
  4. 4. Download the appropriate CU from the Microsoft Update Catalog or Microsoft Download Center
  5. 5. Run the CU installer on all SharePoint servers in the farm, following the standard CU installation sequence (install on app servers first, then WFE servers)
  6. 6. After installation, run the SharePoint Products Configuration Wizard (PSConfig) on each server
  7. 7. Verify the build version has been updated to 16.0.19725.20434 or higher
  8. 8. Test critical SharePoint workflows to ensure functionality is intact
Caveat Cumulative Updates are generally safe but always test in a staging environment first; ensure backup of farm configuration before applying

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $900. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-62826 — 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-62826 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