Security News

Cybersecurity news aggregator

🪟
HIGH Vulnerabilities Microsoft Security Response Center

CVE-2026-33120 Microsoft SQL Server Remote Code Execution Vulnerability

CVE-2026-33120 is an Important-severity remote code execution vulnerability (CVSS 8.8) in Microsoft SQL Server caused by an untrusted pointer dereference, allowing an authenticated low-privileged attacker to execute arbitrary code over the network and gain sysadmin privileges. The article instructs users to update their relevant version of SQL Server, referencing a knowledge base article for version identification, but does not provide specific affected or fixed version numbers.
Read Full Article →

We use optional cookies to improve your experience on our websites, such as through social media connections, and to display personalized advertising based on your online activity. If you reject optional cookies, only cookies necessary to provide you the services will be used. You may change your selection by clicking “Manage Cookies” at the bottom of the page. Privacy Statement Third-Party Cookies Accept Reject Manage cookies MSRC  Customer Guidance  Security Update Guide  Vulnerabilities  CVE-2026-33120 Microsoft SQL Server Remote Code Execution Vulnerability New On this page  CVE-2026-33120  Subscribe RSS PowerShell  API  CSAF Security Vulnerability Released: Apr 14, 2026 Assigning CNA Microsoft CVE.org link CVE-2026-33120  Impact Remote Code Execution Max Severity Important Weakness CWE-822: Untrusted Pointer Dereference CVSS Source Microsoft Vector String CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C Metrics CVSS:3.1 8.8 / 7.7  Base score metrics: 8.8 / Temporal score metrics: 7.7  Expand all  Collapse all Metric Value   Base score metrics(8) Attack Vector Network Attack Complexity Low Privileges Required Low User Interaction None Scope Unchanged Confidentiality High Integrity High Availability High   Temporal score metrics(3) Exploit Code Maturity Unproven Remediation Level Official Fix Report Confidence Confirmed Please see Common Vulnerability Scoring System for more information on the definition of these metrics. Executive Summary Untrusted pointer dereference in SQL Server allows an authorized attacker to execute code over a network. Exploitability The following table provides an exploitability assessment for this vulnerability at the time of original publication. Publicly disclosed No Exploited No Exploitability assessment Exploitation Less Likely FAQ What privileges could be gained by an attacker who successfully exploited the vulnerability? An attacker who successfully exploited this vulnerability could gain SQL sysadmin privileges. I am running SQL Server on my system. What action do I need to take? Update your relevant version of SQL Server. Any applicable driver fixes are included in those updates. There are GDR and/or CU (Cumulative Update) updates offered for my version of SQL Server. How do I know which update to use? First, determine your SQL Server version number. For more information on determining your SQL Server version number, see Microsoft Knowledge Base Article 321185 - How to determine the version, edition, and update level of SQL Server and its components. Second, in the following table, locate your version number or the version range that your version number falls within. The corresponding update is the one you need to install. Note If your SQL Server version number is not represented in the table below, your SQL Server version is no longer supported. Please upgrade to the latest Service Pack or SQL Server product to apply this and future security updates. Update Number Title Version Apply if current product version is… This security update also includes servicing releases up through… 5083245 Security update for SQL Server 2025 CU3+GDR 17.0.4030.1 17.0.4006.2 - 17.0.4025.3 KB5077896 - Previous SQL2025 RTM CU3 5084814 Security update for SQL Server 2025 RTM+GDR 17.0.1110.1 17.0.1000.7 - 17.0.1105.2 KB5077468 - Previous SQL2025 RTM GDR 5083252 Security update for SQL Server 2022 CU24+GDR 16.0.4250.1 16.0.4003.1 - 16.0.4245.2 KB5080999 - Previous SQL2022 RTM CU24 5084815 Security update for SQL Server 2022 RTM+GDR 16.0.1175.1 16.0.1000.6 - 16.0.1170.5 KB5077465 - Previous SQL2022 RTM GDR 5084816 Security update for SQL Server 2019 CU32+GDR 15.0.4465.1 15.0.4003.23 - 15.0.4460.4 KB 5077469 - Previous SQL2019 RTM CU32 GDR 5084817 Security update for SQL Server 2019 RTM+GDR 15.0.2165.1 15.0.2000.5 - 15.0.2160.4 KB 5077470 - Previous SQL2019 RTM GDR 5084818 Security update for SQL Server 2017 CU31+GDR 14.0.3525.1 14.0.3006.16 - 14.0.3520.4 KB 5077471 - Previous SQL2017 RTM CU31 GDR 5084819 Security update for SQL Server 2017 RTM+GDR 14.0.2105.1 14.0.1000.169 - 14.0.2100.4 KB 5077472 - Previous SQL2017 RTM GDR 5084820 Security update for SQL Server 2016 Azure Connect Feature Pack+GDR 13.0.7080.1 13.0.7000.253 - 13.0.7075.5 KB 5077473 - Previous SQL2016 Azure Connect Feature Pack GDR 5084821 Security update for SQL Server 2016 SP3+GDR 13.0.6485.1 13.0.6300.2 - 13.0.6480.4 KB 5077474 - Previous SQL2016 RTM GDR What are the GDR and CU update designations and how do they differ? The General Distribution Release (GDR) and Cumulative Update (CU) designations correspond to the two different servicing options in place for SQL Server baseline releases. A baseline can be either an RTM release or a Service Pack release. GDR updates – cumulatively only contain security updates for the given baseline. CU updates – cumulatively contain all functional fixes and security updates for the given baseline. For any given baseline, either the GDR or CU updates could be options (see below). If SQL Server installation is at a baseline version, you can choose either the GDR or CU update. If SQL Server installation has intentionally only installed past GDR updates, then choose to install the GDR update package. If SQL Server installation has intentionally installed previous CU updates, then choose to install the CU security update package. Note: You are allowed to make a change from GDR updates to CU updates ONE TIME. Once a SQL Server CU update is applied to a SQL Server installation, there is NO way to go back to the GDR update path. Can the security updates be applied to SQL Server instances on Windows Azure (IaaS)? Yes. SQL Server instances on Windows Azure (IaaS) can be offered the security updates through Microsoft Update, or customers can download the security updates from Microsoft Download Center and apply them manually. Acknowledgements David Hayman Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure. See Acknowledgements for more information. Security Updates To determine the support lifecycle for your software, see the Microsoft Support Lifecycle. Release date Descending  Edit columns  Download  Filters  Product Family  Max Severity  Impact  Platform   Clear Release date  Product Platform Impact Max Severity Article Download Build Number Assigning CNA Customer Action Required Title: Release date, Content: Apr 14, 2026 Microsoft SQL Server 2022 for x64-based Systems (GDR) - Remote Code Execution Important Title: Knowledge Base Articles for Microsoft SQL Server 2022 for x64-based Systems (GDR), Content:, 1 link 5084815  Title: Download Security Update for Microsoft SQL Server 2022 for x64-based Systems (GDR), Content:, 1 link Security Update  Title: Build numbers, Content: 16.0.1175.1 Title: Assigning CNA, Content: Microsoft Title: Customer action required, Content: Required All results loaded Loaded all 1 rows Disclaimer The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply. Revisions version revisionDate description 1.0 Apr 14, 2026 Information published.  How satisfied are you with the MSRC Security Update Guide? Rating  Broken  Bad  Below average  Average  Great!  Your Privacy Choices Consumer Health Privacy

Share this article