dbcve.org
Sql Server 2016Application · Microsoft

CVE-2026-32176

HIGH · 7.8 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 13.0.6485.1 / 13.0.7080.1 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL injection vulnerability in Microsoft SQL Server allows an authorized attacker to execute arbitrary SQL commands and escalate privileges locally. The vulnerability stems from improper neutralization of special elements in SQL queries, enabling privilege escalation beyond the attacker's current authorized permissions.

MitigationImplement parameterized queries or prepared statements for all SQL operations, apply least-privilege principles to database roles and permissions, and apply vendor patches when available. Review and restrict database user permissions to the minimum required for their functions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sql Server 2016Application
Affected:>= 13.0.6300.2, < 13.0.6485.1>= 13.0.7000.253, < 13.0.7080.1
Sql Server 2017Application
Affected:>= 14.0.1000.169, < 14.0.2105.1>= 14.0.3006.16, < 14.0.3525.1
Sql Server 2019Application
Affected:>= 15.0.2000.5, < 15.0.2165.1>= 15.0.4003.23, < 15.0.4465.1
Sql Server 2022Application
Affected:>= 16.0.1000.6, < 16.0.1175.1>= 16.0.4003.1, < 16.0.4250.1
Sql Server 2025Application
Affected:>= 17.0.1000.7, < 17.0.1110.1>= 17.0.4006.2, < 17.0.4030.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Retrieve SQL Server version
    Run SELECT @@VERSION; or SELECT SERVERPROPERTY('ProductVersion'); in a SQL query window
    Affected if The version returned falls within any of these ranges: 13.0.6300.2 to 13.0.6485.1, 13.0.7000.253 to 13.0.7080.1 (SQL 2016); 14.0.1000.169 to 14.0.2105.1, 14.0.3006.16 to 14.0.3525.1 (SQL 2017); 15.0.2000.5 to 15.0.2165.1, 15.0.4003.23 to 15.0.4465.1 (SQL 2019); 16.0.1000.6 to 16.0.1175.1, 16.0.4003.
  2. Confirm SQL Server major version
    Run SELECT SERVERPROPERTY('ProductMajorVersion'); to get the numeric major version (13, 14, 15, 16, or 17)
    Affected if The returned major version is 13 (2016), 14 (2017), 15 (2019), 16 (2022), or 17 (2025) and the full version matches the affected ranges in step 1
  3. Identify dynamic SQL execution patterns
    Review application code and stored procedures for use of EXEC(), sp_executesql, or string concatenation in SQL queries; check sys.dm_exec_sql_text for recent ad-hoc queries
    Affected if Dynamic SQL execution without parameterized queries is present and the SQL Server version is vulnerable as per steps 1-2
  4. Assess current user privileges
    Run SELECT SUSER_SNAME(); SELECT IS_SRVROLEMEMBER('sysadmin'); SELECT HAS_PERMS_BY_NAME(NULL, NULL, 'ANY'); to determine current user context
    Affected if The current user has limited privileges and the SQL Server version is in the affected range, making privilege escalation possible

You are affected if your SQL Server version falls within any of the listed vulnerable version ranges AND your applications or stored procedures use dynamic SQL that could be exploited for privilege escalation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 13.0.6485.1 / 13.0.7080.1 / 14.0.2105.1 or later
Fixed in 13.0.6485.113.0.7080.114.0.2105.1
Interim mitigation

Implement parameterized queries or prepared statements for all SQL operations, apply least-privilege principles to database roles and permissions, and apply vendor patches when available. Review and restrict database user permissions to the minimum required for their functions.

Recommended fix High confidence

SQL Server 2016 to 13.0.6485.1 (RTM) or 13.0.7080.1 (SP2); SQL Server 2017 to 14.0.2105.1 (RTM) or 14.0.3525.1; SQL Server 2019 to 15.0.2165.1 or 15.0.4465.1; SQL Server 2022 to 16.0.1175.1 or 16.0.4250.1; SQL Server 2025 to 17.0.1110.1 or 17.0.4030.1

  1. 1. Identify the current SQL Server version by running: SELECT @@VERSION
  2. 2. Determine the appropriate upgrade path based on the current version (2016, 2017, 2019, 2022, or 2025)
  3. 3. Download and apply the latest Cumulative Update (CU) or Service Stack Upgrade (SSU) that meets or exceeds the fixed version for your branch
  4. 4. For SQL Server 2016: Upgrade to version 13.0.6485.1 (RTM branch) or 13.0.7080.1 (SP2 branch)
  5. 5. For SQL Server 2017: Upgrade to version 14.0.2105.1 (RTM branch) or 14.0.3525.1 (CU31 branch)
  6. 6. For SQL Server 2019: Upgrade to version 15.0.2165.1 (RTM branch) or 15.0.4465.1 (CU24 branch)
  7. 7. For SQL Server 2022: Upgrade to version 16.0.1175.1 (RTM branch) or 16.0.4250.1 (CU24 branch)
  8. 8. For SQL Server 2025: Upgrade to version 17.0.1110.1 (RTM branch) or 17.0.4030.1 (CU16 branch)
Caveat Review Microsofts SQL Server release notes for any behavior changes between your current version and the target CU; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sql Server 2016 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32176 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32176 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data