dbcve.org
Sql Server 2016Application · Microsoft

CVE-2026-32167

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 SQL Server allows an authorized attacker to inject malicious SQL commands through improper input handling, potentially executing with elevated privileges. The vulnerability is local in nature, requiring the attacker to have existing authorized access to the system.

MitigationImplement parameterized queries/prepared statements for all database operations, apply least privilege principles to database accounts, and conduct code review to identify and remediate all SQL injection points.

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. Identify installed SQL Server version
    Run 'SELECT @@VERSION' in SQL Server Management Studio or execute 'sqlcmd -S <server> -Q "SELECT @@VERSION"' from command line
    Affected if The version falls within any of the affected ranges: 2016 (13.0.6300.2 to 13.0.6485.1 or 13.0.7000.253 to 13.0.7080.1), 2017 (14.0.1000.169 to 14.0.2105.1 or 14.0.3006.16 to 14.0.3525.1), 2019 (15.0.2000.5 to 15.0.2165.1 or 15.0.4003.23 to 15.0.4465.1), 2022 (16.0.1000.6 to 16.0.1175.1 or 16.0.4003.
  2. Locate custom stored procedures accepting user input
    Query sys.sql_modules for procedures containing dynamic SQL (EXEC/EXECUTE with string concatenation): 'SELECT name, definition FROM sys.sql_modules WHERE definition LIKE "%EXEC%" AND definition LIKE "%+%"'
    Affected if Custom stored procedures build SQL queries through string concatenation rather than parameterized commands
  3. Identify applications using inline SQL with user-supplied data
    Review application source code for direct string building in SQL queries, focusing on areas accepting user input (search fields, filters, form submissions)
    Affected if Application code constructs SQL queries by concatenating user input directly into query strings
  4. Check for overly privileged database roles
    Run 'SELECT member_role, principal_name, type_desc FROM (SELECT rm.member_principal_id, rm.role_principal_id, dp1.name AS principal_name, dp2.name AS member_role, dp2.type_desc FROM sys.database_role_members rm JOIN sys.database_principals dp1 ON rm.member_principal_id = dp1.principal_id JOIN sys.database_principals dp2 ON rm.role_principal_id = dp2.principal_id) WHERE member_role IN ( "db_owner", "db_securityadmin", "sysadmin")'
    Affected if Database accounts with elevated roles (db_owner, db_securityadmin, sysadmin) are used by applications that may be vulnerable to SQL injection

Your environment is affected if the SQL Server version matches the affected ranges AND applications or stored procedures use dynamic SQL built from user input without parameterization.

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/prepared statements for all database operations, apply least privilege principles to database accounts, and conduct code review to identify and remediate all SQL injection points.

Recommended fix High confidence

Upgrade to the latest cumulative update for your SQL Server version branch (e.g., SQL Server 2019 to 15.0.4465.1 or later, SQL Server 2022 to 16.0.4250.1 or later)

  1. 1. Identify the current SQL Server version by running: SELECT @@VERSION;
  2. 2. Determine which version branch your current installation falls into based on the affected ranges provided
  3. 3. Plan a maintenance window for the upgrade operation
  4. 4. Perform full database backups before upgrading
  5. 5. Download and install the appropriate cumulative update or service pack that matches your version branch: For 2016: 13.0.6485.1 or 13.0.7080.1; For 2017: 14.0.2105.1 or 14.0.3525.1; For 2019: 15.0.2165.1 or 15.0.4465.1; For 2022: 16.0.1175.1 or 16.0.4250.1; For 2025: 17.0.1110.1 or 17.0.4030.1
  6. 6. Apply the update using SQL Server Setup or appropriate installer
  7. 7. Verify the version has been updated by running SELECT @@VERSION;
  8. 8. Test critical database operations and applications to ensure functionality
Caveat Standard SQL Server upgrade considerations apply - test in non-production first, ensure compatibility with existing applications and features

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

Fix this in Sql Server 2016 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32167 — 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-32167 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