dbcve.org
Sql Server 2016Application · Microsoft

CVE-2026-26116

HIGH · 8.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 13.0.6480.4 / 13.0.7075.5 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 over a network.

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

This is a SQL injection vulnerability in Microsoft SQL Server where improper neutralization of special elements in SQL commands allows an authenticated attacker to elevate privileges. An authorized user can inject malicious SQL statements through input fields to gain higher-level database access.

MitigationMitigation involves using parameterized queries or prepared statements instead of dynamic SQL, implementing strict input validation, applying least privilege principles to database accounts, and conducting code review to identify and remediate all 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.6480.4>= 13.0.7000.253, < 13.0.7075.5
Sql Server 2017Application
Affected:>= 14.0.1000.169, < 14.0.2100.4>= 14.0.3006.16, < 14.0.3520.4
Sql Server 2019Application
Affected:>= 15.0.2000.5, < 15.0.2160.4>= 15.0.4003.23, < 15.0.4460.4
Sql Server 2022Application
Affected:>= 16.0.1000.6, < 16.0.1170.5>= 16.0.4003.1, < 16.0.4240.4
Sql Server 2025Application
Affected:>= 17.0.1000.7, < 17.0.1105.2>= 17.0.4006.2, < 17.0.4020.2

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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; in SQL Server Management Studio or via sqlcmd
    Affected if Version number falls within any of the affected ranges: 13.0.6300.2 to 13.0.6480.4, 13.0.7000.253 to 13.0.7075.5, 14.0.1000.169 to 14.0.2100.4, 14.0.3006.16 to 14.0.3520.4, 15.0.2000.5 to 15.0.2160.4, 15.0.4003.23 to 15.0.4460.4, 16.0.1000.6 to 16.0.1170.5, 16.0.4003.1 to 16.0.4240.4, 17.0.1000.7 to
  2. Identify applications using dynamic SQL
    Search application source code for patterns like EXEC() or sp_executesql with string concatenation, and review stored procedures that construct SQL statements from user input
    Affected if Application code concatenates user input directly into SQL queries without using parameterized queries or stored procedure parameters
  3. Audit input handling in database queries
    Examine query code paths where user-supplied data flows into SQL statements, looking for absence of parameterized query usage
    Affected if User input is passed directly to SQL execution functions without parameter binding
  4. Review database user privileges
    Run SELECT name, type_desc, is_disabled FROM sys.server_principals; to list server logins and check which accounts have elevated permissions
    Affected if Application database accounts have more privileges than necessary, allowing privilege escalation upon successful injection
  5. Check for SQL injection-safe coding patterns
    Inspect stored procedures and application code for use of parameterized queries, sp_executesql with parameters, or prepared statements
    Affected if Code relies on string concatenation or dynamic SQL construction without parameterization, making injection possible

Your environment is affected if the SQL Server version falls within the listed vulnerable ranges AND applications use dynamic SQL with direct user input concatenation rather than parameterized queries.

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.6480.4 / 13.0.7075.5 / 14.0.2100.4 or later
Fixed in 13.0.6480.413.0.7075.514.0.2100.4
Interim mitigation

Mitigation involves using parameterized queries or prepared statements instead of dynamic SQL, implementing strict input validation, applying least privilege principles to database accounts, and conducting code review to identify and remediate all injection points.

Recommended fix High confidence

Upgrade to the latest cumulative update for your SQL Server version branch (2016: CU5, 2017: CU30, 2019: CU30, 2022: CU19, 2025: CU4)

  1. Identify your current SQL Server version by running: SELECT @@VERSION
  2. Determine which version branch you are on (e.g., RTM, Service Pack 3 for 2016, CU6/CU16 for 2019, etc.)
  3. For SQL Server 2016: Upgrade to either SP3 CU4 (13.0.6480.4) or SP3 CU5 (13.0.7075.5) - choose the higher CU available for your branch
  4. For SQL Server 2017: Upgrade to either CU20 (14.0.2100.4) or CU30 (14.0.3520.4) - choose the higher CU available for your branch
  5. For SQL Server 2019: Upgrade to either CU25 (15.0.2160.4) or CU30 (15.0.4460.4) - choose the higher CU available for your branch
  6. For SQL Server 2022: Upgrade to either CU14 (16.0.1170.5) or CU19 (16.0.4240.4) - choose the higher CU available for your branch
  7. For SQL Server 2025: Upgrade to either CU2 (17.0.1105.2) or CU4 (17.0.4020.2) - choose the higher CU available for your branch
  8. Download and install the appropriate cumulative update from https://learn.microsoft.com/en-us/sql/database-engine/install-windows/latest-updates-for-microsoft-sql-server
Caveat Standard cumulative update risks apply - test thoroughly; some updates may require restart of SQL Server service

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
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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