Skip to content

CVE-2026-40370

Microsoft SQL Server 2016 path traversal

8.8 HIGHEPSS 1.01%
  1. Published12 May 2026

Description

External control of file name or path in SQL Server allows an authorized attacker to execute code over a network.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredLow
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

Microsoft SQL Server 2016≥ 13.0.6300.2 < 13.0.6490.1 · ≥ 13.0.7000.253 < 13.0.7085.1
Microsoft SQL Server 2017≥ 14.0.1000.169 < 14.0.2110.2 · ≥ 14.0.3006.16 < 14.0.3530.2
Microsoft SQL Server 2019≥ 15.0.2000.5 < 15.0.2170.1 · ≥ 15.0.4003.23 < 15.0.4470.1
Microsoft SQL Server 2022≥ 16.0.1000.6 < 16.0.1180.1 · ≥ 16.0.4003.1 < 16.0.4252.3
Microsoft SQL Server 2025≥ 17.0.1000.7 < 17.0.1115.1 · ≥ 17.0.4006.2 < 17.0.4040.1

Remediation

Fixed in
Microsoft SQL Server 2016≥ 13.0.6490.1
Microsoft SQL Server 2017≥ 14.0.2110.2
Microsoft SQL Server 2019≥ 15.0.2170.1
Microsoft SQL Server 2022≥ 16.0.1180.1
Microsoft SQL Server 2025≥ 17.0.1115.1

Frequently asked

Is CVE-2026-40370 being actively exploited?

CVE-2026-40370 is not in the CISA KEV catalog. Its EPSS exploit probability is 1.01%.

How severe is CVE-2026-40370?

CVE-2026-40370 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 1.01% probability of exploitation.

Which products are affected by CVE-2026-40370?

Affected products include Microsoft SQL Server 2016, Microsoft SQL Server 2017, Microsoft SQL Server 2019, Microsoft SQL Server 2022, Microsoft SQL Server 2025.

How do I fix CVE-2026-40370?

Upgrade affected software to a fixed version, for example Microsoft SQL Server 2016 13.0.6490.1, Microsoft SQL Server 2017 14.0.2110.2, Microsoft SQL Server 2019 15.0.2170.1 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-40370 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.