dbcve.org
Sql Server 2016Application · Microsoft

CVE-2026-40370

HIGH · 8.8 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 13.0.6490.1 / 13.0.7085.1 or later.
See remediation →
94/100
Remediation priority · Urgent
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
External control of file name or path in SQL Server 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 confidence

A path traversal vulnerability in Microsoft SQL Server allows an authenticated attacker to manipulate file paths, potentially leading to arbitrary code execution. The vulnerability stems from insufficient validation of user-supplied file path inputs, enabling an attacker with valid SQL Server credentials to escape intended directory restrictions and execute malicious code.

MitigationApply the latest Microsoft SQL Server security updates as they become available. Additionally, enforce least-privilege principles for SQL Server accounts and disable xp_cmdshell and other potentially dangerous extended stored procedures unless explicitly required.

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
Sql Server 2016Application
Affected:>= 13.0.6300.2, < 13.0.6490.1>= 13.0.7000.253, < 13.0.7085.1
Sql Server 2017Application
Affected:>= 14.0.1000.169, < 14.0.2110.2>= 14.0.3006.16, < 14.0.3530.2
Sql Server 2019Application
Affected:>= 15.0.2000.5, < 15.0.2170.1>= 15.0.4003.23, < 15.0.4470.1
Sql Server 2022Application
Affected:>= 16.0.1000.6, < 16.0.1180.1>= 16.0.4003.1, < 16.0.4252.3
Sql Server 2025Application
Affected:>= 17.0.1000.7, < 17.0.1115.1>= 17.0.4006.2, < 17.0.4040.1

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
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 checks

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

  1. Determine installed SQL Server version
    Run the query SELECT @@VERSION; in SQL Server Management Studio or via sqlcmd. This returns the exact version number including build information.
    Affected if The reported version falls within any of the affected ranges: 13.0.6300.2 to 13.0.6490.1, 13.0.7000.253 to 13.0.7085.1 (SQL 2016); 14.0.1000.169 to 14.0.2110.2, 14.0.3006.16 to 14.0.3530.2 (SQL 2017); 15.0.2000.5 to 15.0.2170.1, 15.0.4003.23 to 15.0.4470.1 (SQL 2019); 16.0.1000.6 to 16.0.1180.1, 16.
  2. Check if xp_cmdshell is enabled
    Run: EXEC sp_configure 'show advanced options', 1; RECONFIGURE; EXEC sp_configure 'xp_cmdshell'; A value of 1 for run_value indicates it is enabled.
    Affected if xp_cmdshell is enabled (run_value = 1), allowing execution of operating system commands via SQL queries which could be chained with path traversal.
  3. Check if OLE Automation Procedures are enabled
    Run: EXEC sp_configure 'show advanced options', 1; RECONFIGURE; EXEC sp_configure 'Ole Automation Procedures'; A value of 1 for run_value indicates it is enabled.
    Affected if OLE Automation Procedures are enabled (run_value = 1), allowing creation of OLE objects that can interact with the file system.
  4. Check if ad hoc distributed queries are enabled
    Run: EXEC sp_configure 'show advanced options', 1; RECONFIGURE; EXEC sp_configure 'ad hoc distributed queries'; A value of 1 for run_value indicates it is enabled.
    Affected if Ad hoc distributed queries are enabled (run_value = 1), allowing OPENROWSET and OPENDATASOURCE calls that could reference arbitrary file paths.
  5. Verify SQL Server service account file system permissions
    Identify the service account via SQL Server Configuration Manager or Services.msc, then use icacls or PowerShell Get-Acl to review what directories that account can read/write. Focus on directories outside the standard SQL data/log folders.
    Affected if The SQL Server service account has broad file system write permissions beyond its necessary data directories, which could be leveraged for path traversal exploitation.

Your environment is affected if the SQL Server version falls within any of the listed affected ranges AND any of the advanced features (xp_cmdshell, OLE Automation, or ad hoc queries) that enable file system manipulation are enabled.

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 13.0.6490.1 / 13.0.7085.1 / 14.0.2110.2 or later
Fixed in 13.0.6490.113.0.7085.114.0.2110.2
Interim mitigation

Apply the latest Microsoft SQL Server security updates as they become available. Additionally, enforce least-privilege principles for SQL Server accounts and disable xp_cmdshell and other potentially dangerous extended stored procedures unless explicitly required.

Recommended fix High confidence

SQL Server 2016 to 13.0.6490.1/13.0.7085.1; SQL Server 2017 to 14.0.2110.2/14.0.3530.2; SQL Server 2019 to 15.0.2170.1/15.0.4470.1; SQL Server 2022 to 16.0.1180.1/16.0.4252.3; SQL Server 2025 to 17.0.1115.1/17.0.4040.1

  1. 1. Identify the current SQL Server version by running 'SELECT @@VERSION' in SQL Server Management Studio
  2. 2. Determine which version branch your current instance falls into (2016, 2017, 2019, 2022, or 2025)
  3. 3. For SQL Server 2016: Upgrade to version 13.0.6490.1 or later (for the 13.0.6300.2 branch) OR upgrade to 13.0.7085.1 or later (for the 13.0.7000.253 branch)
  4. 4. For SQL Server 2017: Upgrade to version 14.0.2110.2 or later (for the 14.0.1000.169 branch) OR upgrade to 14.0.3530.2 or later (for the 14.0.3006.16 branch)
  5. 5. For SQL Server 2019: Upgrade to version 15.0.2170.1 or later (for the 15.0.2000.5 branch) OR upgrade to 15.0.4470.1 or later (for the 15.0.4003.23 branch)
  6. 6. For SQL Server 2022: Upgrade to version 16.0.1180.1 or later (for the 16.0.1000.6 branch) OR upgrade to 16.0.4252.3 or later (for the 16.0.4003.1 branch)
  7. 7. For SQL Server 2025: Upgrade to version 17.0.1115.1 or later (for the 17.0.1000.7 branch) OR upgrade to 17.0.4040.1 or later (for the 17.0.4006.2 branch)
  8. 8. Download and apply the appropriate Cumulative Update (CU) from Microsoft's SQL Server updates page
Caveat Standard SQL Server CU updates are typically low-risk rollups; review release notes for any known issues affecting your specific configuration

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

Fix this in Sql Server 2016 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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