Read the docs

Command injection in Microsoft SQL Server allows code execution

Priority MEDIUM 42CWE-77Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Required
Attack complexity
Low
Impact type
Code execution
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and Microsoft. Impact type from Microsoft.

Summary

Several Microsoft SQL Server 2017, 2019, 2022 and 2025 builds are affected. Improper neutralization of special elements in a command (CWE-77) lets an unauthorized attacker execute code over a network. A user must take an action for the attack to succeed. Microsoft rates exploitation as less likely and reports no public disclosure.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

Description from the CNA

Improper neutralization of special elements used in a command ('command injection') in SQL Server allows an unauthorized attacker to execute code over a network.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00915 60th percentileScored 2026-11-16
Fix Fixed Microsoft: 8 updates

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
MicrosoftMicrosoft SQL Server 2017 (GDR)14.0.0 to before 14.0.2150.214.0.2150.2Patch availableCNA
MicrosoftMicrosoft SQL Server 2017 for x64-based Systems (CU31)14.0.3006.16 to before 14.0.3570.214.0.3570.2Patch availableCNA
MicrosoftMicrosoft SQL Server 2019 (GDR)15.0.0 to before 15.0.2210.415.0.2210.4Patch availableCNA
MicrosoftMicrosoft SQL Server 2019 for x64-based Systems (CU32)15.0.4003.23 to before 15.0.4510.215.0.4510.2Patch availableCNA
MicrosoftMicrosoft SQL Server 2022 (GDR)16.0.0 to before 16.0.1220.316.0.1220.3Patch availableCNA
MicrosoftMicrosoft SQL Server 2022 for x64-based Systems (CU27)16.0.4003.1 to before 16.0.4315.216.0.4315.2Patch availableCNA
MicrosoftMicrosoft SQL Server 2025 CU1017.0.4006.0 to before 17.0.5045.317.0.5045.3Patch availableCNA
MicrosoftMicrosoft SQL Server 2025 for x64-based Systems (GDR)17.0.1050.2 to before 17.0.1155.317.0.1155.3Patch availableCNA
  • Microsoft SQL Server 2017 (GDR) VendorMicrosoft Affected 14.0.0 to before 14.0.2150.2 Fixed in 14.0.2150.2 Patch available CNA
  • Microsoft SQL Server 2017 for x64-based Systems (CU31) VendorMicrosoft Affected 14.0.3006.16 to before 14.0.3570.2 Fixed in 14.0.3570.2 Patch available CNA
  • Microsoft SQL Server 2019 (GDR) VendorMicrosoft Affected 15.0.0 to before 15.0.2210.4 Fixed in 15.0.2210.4 Patch available CNA
  • Microsoft SQL Server 2019 for x64-based Systems (CU32) VendorMicrosoft Affected 15.0.4003.23 to before 15.0.4510.2 Fixed in 15.0.4510.2 Patch available CNA
  • Microsoft SQL Server 2022 (GDR) VendorMicrosoft Affected 16.0.0 to before 16.0.1220.3 Fixed in 16.0.1220.3 Patch available CNA
  • Microsoft SQL Server 2022 for x64-based Systems (CU27) VendorMicrosoft Affected 16.0.4003.1 to before 16.0.4315.2 Fixed in 16.0.4315.2 Patch available CNA
  • Microsoft SQL Server 2025 CU10 VendorMicrosoft Affected 17.0.4006.0 to before 17.0.5045.3 Fixed in 17.0.5045.3 Patch available CNA
  • Microsoft SQL Server 2025 for x64-based Systems (GDR) VendorMicrosoft Affected 17.0.1050.2 to before 17.0.1155.3 Fixed in 17.0.1155.3 Patch available CNA

Remediation

Install the fixed builds: SQL Server 2017 (GDR) 14.0.2150.2, SQL Server 2017 for x64-based Systems (CU31) 14.0.3570.2, SQL Server 2019 (GDR) 15.0.2210.4, SQL Server 2019 for x64-based Systems (CU32) 15.0.4510.2, SQL Server 2022 (GDR) 16.0.1220.3, SQL Server 2022 for x64-based Systems (CU27) 16.0.4315.2, SQL Server 2025 CU10 17.0.5045.3 and SQL Server 2025 for x64-based Systems (GDR) 17.0.1155.3. Microsoft advisories KB5129299, KB5129300, KB5132745, KB5132746, KB5132747, KB5132748, KB5132749 and KB5132751 list these fixes.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

Microsoft 8 updates

  • Security Update
    • Microsoft SQL Server 2019 for x64-based Systems (GDR) 15.0.2210.4
  • Security Update
    • Microsoft SQL Server 2017 for x64-based Systems (GDR) 14.0.2150.2
  • Security Update
    • Microsoft SQL Server 2025 for x64-based Systems (GDR) 17.0.1155.3
Show 5 more Microsoft updates
  • Security Update
    • Microsoft SQL Server 2022 for x64-based Systems (GDR) 16.0.1220.3
  • Security Update
    • Microsoft SQL Server 2017 for x64-based Systems (CU31) 14.0.3570.2
  • Security Update
    • Microsoft SQL Server 2019 for x64-based Systems (CU32) 15.0.4510.2
  • Security Update
    • Microsoft SQL Server 2022 for x64-based Systems (CU27) 16.0.4315.2
  • Security Update
    • Microsoft SQL Server 2025 for x64-based Systems CU10 17.0.5045.3

Vendor assessments

Microsoft

Microsoft's page for this CVE →

Impact
Remote Code Execution
Exploited
No
Publicly disclosed
No
Exploitability
Exploitation Less Likely

Timeline

  1. 2026-11-10 Threatist record created from CVE-2026-116930
  2. 2026-11-10 CISA SSVC decision points changed
  3. 2026-11-10 Priority changed: MEDIUM → LOW
  4. 2026-11-10 Alias added: GHSA-mh4r-vcm9-277m
  5. 2026-11-11 Fix available: KB5129299, KB5129300, KB5132745 +5 · Microsoft
  6. 2026-11-12 Priority changed: LOW → MEDIUM

References

  • TI-2026-42212 Unsafe deserialization in Microsoft SharePoint allows code execution KEVCVSS 3.1CRITICAL 9.8
  • TI-2026-37256 Deserialization flaw in Microsoft SharePoint allows code execution KEVCVSS 3.1CRITICAL 9.8
  • TI-2026-26194 Windows IKE Service Extensions Remote Code Execution Vulnerability KEVCVSS 3.1CRITICAL 9.8
  • TI-2026-16982 Deserialization flaw in Microsoft SharePoint allows code execution KEVCVSS 3.1CRITICAL 9.8
  • TI-2025-36863 Remote code execution in Windows Server Update Service KEVCVSS 3.1CRITICAL 9.8
  • TI-2025-33671 Deserialization flaw in Microsoft SharePoint lets attackers run code KEVCVSS 3.1CRITICAL 9.8
See all 19148 →

Sources