What is the CVSS score of CVE-2026-47296?

CVE-2026-47296 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.6%.

Which versions of Microsoft SQL Server are affected by CVE-2026-47296?

Microsoft SQL Server versions 2016 through 2025 contain a SQL injection vulnerability (CVE-2026-47296) that allows authenticated database users to escalate to administrative privileges.. A patch is available.

Is there a public PoC exploit available for CVE-2026-47296?

Yes, a public proof-of-concept exploit is available for CVE-2026-47296. Prioritise patching immediately. EPSS: 0.6%.

How to fix or mitigate CVE-2026-47296?

Within 24 hours: Conduct a complete inventory of SQL Server 2016-2025 instances and document all database user accounts, prioritizing production and high-sensitivity databases. Within 7 days: Deploy vendor-released patches to all affected instances, staging updates for production systems with scheduled maintenance windows. Within 30 days: Review database access logs for suspicious authentication or privilege escalation attempts, confirm all patches applied successfully, and validate that normal application functionality is restored.

Microsoft SQL Server CVE-2026-47296

EUVD-2026-43967 HIGH

SQL Injection (CWE-89)

2026-07-14 microsoft

GHSA-448r-r56x-9vhx

SQLi Microsoft Microsoft Sql Server 2016 Service Pack 3 Gdr Microsoft Sql Server 2016 Service Pack 3 Azure Connect Feature Pack Microsoft Sql Server 2017 Cu 31 Microsoft Sql Server 2017 Gdr Microsoft Sql Server 2019 Cu 32 Microsoft Sql Server 2019 Gdr Microsoft Sql Server 2022 Gdr Microsoft Sql Server 2025 For X64 Based Systems Gdr Microsoft Sql Server 2022 For X64 Based Systems Cu 25 Microsoft Sql Server 2025 Cu 6

7.5

CVSS 3.1 · NVD

Severity by source

Vendor (microsoft) PRIMARY

HIGH

qualitative

NVD

7.5 HIGH

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

ENISA EUVD

HIGH

qualitative

vuln.today AI

7.5 HIGH

PR:L for required authenticated SQL access; AC:H for specific triggerable injection path; AV:N as SQL connections traverse the network even when privilege impact is server-local.

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

4.0 AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Updated

Aug 04, 2026 - 00:31 vuln.today

v2 (cvss_changed)

Re-analysis Queued

Aug 04, 2026 - 00:22 vuln.today

cvss_changed

CVSS changed

Aug 04, 2026 - 00:22 NVD

7.8 (HIGH) 7.5 (HIGH)

Analysis Generated

Jul 14, 2026 - 17:35 vuln.today

CVE Published

Jul 14, 2026 - 17:04 nvd

HIGH 7.8

DescriptionNVD

Improper neutralization of special elements used in an sql command ('sql injection') in SQL Server allows an authorized attacker to elevate privileges locally.

AnalysisAI

SQL injection in Microsoft SQL Server (versions 2016 through 2025) enables an authenticated attacker to escalate privileges on the database server. The flaw, tracked as CWE-89, exists within the SQL Server engine's handling of user-supplied SQL input, allowing insufficient neutralization to be leveraged for privilege elevation. Publicly available exploit code exists (GitHub gist), though CISA has not yet added this to the KEV catalog and SSVC indicates no confirmed active exploitation; EPSS sits at 0.57% (44th percentile), suggesting low but non-trivial opportunistic exploitation risk.

Technical ContextAI

CWE-89 (Improper Neutralization of Special Elements in SQL Commands) describes a failure to sanitize user-controlled input before it is incorporated into a SQL query, enabling an attacker to alter the query's logic. In this instance the injection surface resides within Microsoft SQL Server's server-side processing - not a web application layer - meaning an authenticated database-level principal can craft SQL that the engine executes with elevated context. The affected CPE strings span cpe:2.3:a:microsoft:microsoft_sql_server_2016_service_pack_3_(gdr) through cpe:2.3:a:microsoft:microsoft_sql_server_2025_for_x64-based_systems_(gdr), confirming the vulnerability is present across five major SQL Server release lines and their respective cumulative update and GDR servicing branches. The attack complexity is rated High (AC:H), indicating that exploitation requires specific conditions beyond simply having a valid connection, likely related to specific stored procedures, internal functions, or schema configurations that expose the injectable path.

RemediationAI

Apply the Microsoft-released patches via the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-47296. Target patch versions per release line are: SQL Server 2016 SP3 GDR → 13.0.6500.1 or later; SQL Server 2016 SP3 Azure Connect Feature Pack → 13.0.7095.1 or later; SQL Server 2017 GDR → 14.0.2120.1 or later; SQL Server 2017 CU 31 → 14.0.3540.1 or later; SQL Server 2019 GDR → 15.0.2180.2 or later; SQL Server 2019 CU 32 → 15.0.4480.2 or later; SQL Server 2022 GDR → 16.0.1190.2 or later; SQL Server 2022 CU 25 → 16.0.4262.2 or later; SQL Server 2025 GDR → 17.0.1125.2 or later; SQL Server 2025 CU 6 → 17.0.4060.2 or later. Where patching cannot occur immediately, compensating controls should include restricting SQL Server logins to only those principals that strictly require access (minimize PR:L attack surface), auditing and revoking unnecessary EXECUTE permissions on stored procedures and extended stored procedures (which are common injection pivot points), enabling SQL Server Audit to log privilege-sensitive operations for anomaly detection, and ensuring SQL Server instances are not internet-exposed - the AC:H constraint means exploitation requires specific knowledge, making network segmentation an effective friction layer. Note that disabling features may impact applications dependent on those stored procedures.