LearnCTEM.com, Best CTEM Learning Platform
CVE Intelligence Hub

CVE-2026-118112: Microsoft SQL Server Code Injection Vulnerability

CVE-2026-118112 explained: high Code Injection in Microsoft SQL Server. CVSS 8. Affected versions, detection, fixes and CTEM priority.

Last updated: Nov 10, 2026

CVSS
8 HIGH
EPSS
n/a
CISA KEV
Not listed
CWE
CWE-94

Sources: National Vulnerability Database, CVE.org, CISA KEV, FIRST EPSS

CVE-2026-118112 Overview

Improper control of generation of code ('code injection') in SQL Server allows an authorized attacker to elevate privileges over a network.

Critical Impact

Remote, authenticated attackers who persuade a user to act can exploit this Code Injection in Microsoft SQL Server. The CVSS base score is 8 (High).

Affected Products

  • Microsoft SQL Server: see the vendor advisory for the exact affected versions

Discovery Timeline

  • 2026-11-10: CVE-2026-118112 published to the National Vulnerability Database by secure@microsoft.com
  • 2026-11-10: last updated in the NVD database

Technical Details for CVE-2026-118112

Vulnerability Analysis

CVE-2026-118112 is a Code Injection weakness (CWE-94: Code Injection) in Microsoft SQL Server. Based on its CVSS vector, the flaw can be reached over the network, needs some level of access, and relies on a user taking an action. Attacker input is executed as program code.

With a CVSS base score of 8, apply the vendor fix and confirm exposure on internet facing and business critical assets first.

Root Cause

The weakness is classified as CWE-94: Code Injection. Attacker input is executed as program code.

Attack Vector

Based on the CVSS vector, the flaw can be reached over the network, needs some level of access, and relies on a user taking an action. Attack complexity is low complexity.

No exploitation in the wild is confirmed by CISA at the time of the last update. Check the references below for any vendor or researcher proof of concept.

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Detection Methods for CVE-2026-118112

Detection Strategies

  • Inventory every instance of Microsoft SQL Server and compare the running version with the affected range above.
  • Check external attack surface scans for internet facing instances of the component.
  • Run an authenticated vulnerability scan once your scanner ships a check for this CVE.

Monitoring Recommendations

  • Forward Microsoft SQL Server application, access and audit logs to your SIEM for retrospective hunting.
  • Alert on new processes, configuration changes or outbound connections from the affected service.
  • Track the vendor advisory and the CISA KEV catalog for changes in exploitation status.

How to Mitigate CVE-2026-118112

Immediate Actions Required

  • Apply the fixed version of Microsoft SQL Server named in the vendor advisory.
  • Prioritize internet facing and business critical instances first.
  • Rescan after the change to confirm the exposure is closed.

Patch Information

Use the fixed version listed in the vendor advisory for Microsoft SQL Server.

Workarounds

  • If patching must wait, restrict network access to the affected service and place it behind authentication or a web application firewall rule.

CWE References

Technical References

This entry is built directly from NVD, CISA KEV and EPSS data. Verify fixed versions in the vendor advisory before you deploy.

Frequently asked questions

CVE-2026-118112 is a high severity Code Injection in Microsoft SQL Server with a CVSS score of 8. Apply the vendor fix and confirm exposure on internet facing and business critical assets first.

Related CVEs

All Microsoft CVEs in 2026
Your next credential

Earn your free CTEM certification.

Learn to scope, prioritize, validate and mobilize fixes for CVEs like CVE-2026-118112 with a free CTEM certification.

Free to takePublicly verifiable

Beginner / Practitioner / Program Leader

Explore certifications