CVE-2026-45454
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 · uneditedImproper limitation of a pathname to a restricted directory ('path traversal') in Microsoft Office SharePoint allows an authorized attacker to execute code 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 confidenceThis is a path traversal vulnerability in Microsoft Office SharePoint where improper path validation allows an authenticated attacker to escape restricted directories and potentially execute arbitrary code over the network. The vulnerability stems from insufficient sanitization of file path inputs, enabling traversal outside intended directory boundaries.
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< 16.0.19725.20384= 2016= 2019CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Verify SharePoint Server is installedCheck for SharePoint services running on the system. In PowerShell, run: Get-Service | Where-Object {$_.DisplayName -like '*SharePoint*'} or check for SharePoint Central Administration site in IIS.Affected if No SharePoint services or components are found, then the system is not affected.
-
Retrieve the SharePoint build versionOpen SharePoint Management Shell (PowerShell) and run: (Get-SPFarm).BuildVersion.ToString() to get the exact build number, or check the registry key: HKLM:\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\Version\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\16.0\Config\VersionAffected if Unable to retrieve a SharePoint version number indicates SharePoint may not be installed.
-
Compare build against affected version rangeCompare the retrieved build version (e.g., 16.0.xxxxx.xxxx) against the affected threshold: versions lower than 16.0.19725.20384 are vulnerable. Also identify if the installation is SharePoint 2016 or 2019.Affected if The installed build is less than 16.0.19725.20384, or the product is SharePoint 2016 or SharePoint 2019.
-
Confirm SharePoint authentication is enabledPath traversal requires an authenticated session. Verify that SharePoint authentication methods are configured in Central Administration under Application Management > Manage web applications > Authentication Providers.Affected if SharePoint is accessible without any authentication, which would not match the authenticated attacker requirement, but the vulnerability still exists in the code path.
A system is affected if it runs Microsoft SharePoint Server with a build version lower than 16.0.19725.20384, or if it is SharePoint Server 2016 or 2019.
Generated from the published advisory. Verify against your own configuration.
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 · scoped16.0.19725.20384
Apply Microsoft security updates for SharePoint when released; in the interim, restrict SharePoint service account permissions to minimum required and monitor for unusual file access patterns.
SharePoint Server 2019/2016 to version 16.0.19725.20384 or later (November 2025 CU or newer)
- Identify your current SharePoint Server version via SharePoint Administration Center or Get-SPFarm command
- For SharePoint Server 2019: Install the November 2025 or later Cumulative Update (CU) which includes the fix build 16.0.19725.20384
- For SharePoint Server 2016: Install the November 2025 or later Cumulative Update (CU) which includes the fix build
- After installing the CU, run the SharePoint Products Configuration Wizard to apply the updates
- Verify the build number has updated to 16.0.19725.20384 or later using Get-SPFarm | Select BuildVersion
- Test critical SharePoint workflows before deploying to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
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 locallyCheck whether your project pulls in CVE-2026-45454 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45454 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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