CVE-2026-40370Network attack vector

Authenticated code execution via externally controlled path

Published May 12, 2026 · Updated May 12, 2026

External file-path control in Microsoft SQL Server allows remote authenticated users to execute code over a network. SQL Server uses an attacker-controlled file name or path across an undisclosed trust boundary; Microsoft has not identified the affected component or operation. A valid low-privilege SQL Server login is required, and successful exploitation executes code on the database server.

CVSS severity8.8
High
EPSS probability0.56%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

External file-path control in Microsoft SQL Server allows remote authenticated users to execute code over a network. SQL Server uses an attacker-controlled file name or path across an undisclosed trust boundary; Microsoft has not identified the affected component or operation. A valid low-privilege SQL Server login is required, and successful exploitation executes code on the database server.

The record

CVE
CVE-2026-40370
Published
May 12, 2026
Updated
May 12, 2026
Vendor
Microsoft
Product
Microsoft SQL Server
Classifications
CWE-73, CWE-610, T1210
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. May 12, 2026CVE publishedPublication date reported by the CVE source.
  2. May 12, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=13.0.0 <13.0.6490.1
  2. Affected versionversion=14.0.0 <14.0.2110.2
  3. Affected versionversion=14.0.0 <14.0.3530.2
  4. Affected versionversion=15.0.0.0 <15.0.4470.1
  5. Affected versionversion=15.0.0 <15.0.2170.1
  6. Affected versionversion=16.0.0.0 <16.0.4252.3
  7. Affected versionversion=16.0.0 <16.0.1180.1
  8. Affected versionversion=17.0.1050.2 <17.0.1115.1
  9. Affected versionversion=17.0.4040.1 <17.0.4040.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Microsoft · Microsoft SQL Serverversion=13.0.0 <13.0.6490.1; version=14.0.0 <14.0.2110.2; version=14.0.0 <14.0.3530.2; version=15.0.0.0 <15.0.4470.1; version=15.0.0 <15.0.2170.1; version=16.0.0.0 <16.0.4252.3; version=16.0.0 <16.0.1180.1; version=17.0.1050.2 <17.0.1115.1; version=17.0.4040.1 <17.0.4040.1
Microsoft · Microsoft SQL Server 2016 Service Pack 3 Azure Connect Feature Packversion=13.0.0 <13.0.7085.1

Published CVSS scores

8.8Microsoft CorporationCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-73External Control of File Name or Path
CWE-610Externally Controlled Reference to a Resource in Another Sphere
T1210Exploitation of Remote Services

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo