dbcve.org
Sql Server 2016Application · Microsoft

CVE-2026-47296

HIGH · 7.5 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 13.0.6500.1 / 13.0.7095.1 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click 5 weeks old

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.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1w ago

Surfaced from public web coverage — external links open in a new tab.

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 an SQL injection vulnerability in Microsoft SQL Server where improper neutralization of special elements in SQL commands allows an authorized attacker to escalate privileges locally. The attacker already has some level of access but can exploit the injection flaw to gain higher privileges within the SQL Server environment.

MitigationMitigate by refactoring vulnerable code to use parameterized queries or stored procedures with proper input validation, applying the principle of least privilege to database accounts, and ensuring database users have only the minimum permissions 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.6500.1>= 13.0.7000.253, < 13.0.7095.1
Sql Server 2017Application
Affected:>= 14.0.1000.169, < 14.0.2120.1>= 14.0.3006.16, < 14.0.3540.1
Sql Server 2019Application
Affected:>= 15.0.2000.5, < 15.0.2180.2>= 15.0.4003.23, < 15.0.4480.2
Sql Server 2022Application
Affected:>= 16.0.1000.6, < 16.0.1190.2>= 16.0.4003.1, < 16.0.4262.2
Sql Server 2025Application
Affected:>= 17.0.1000.7, < 17.0.1125.2>= 17.0.4006.2, < 17.0.4060.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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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. Determine SQL Server version
    Run SELECT @@VERSION in SQL Server Management Studio or via sqlcmd to retrieve the exact build number
    Affected if The version falls within any of the affected ranges listed for 2016, 2017, 2019, 2022, or 2025
  2. Identify dynamic SQL execution patterns
    Query sys.sql_modules or inspect application code for use of EXEC() or sp_executesql with string concatenation rather than parameterized queries
    Affected if Vulnerable dynamic SQL patterns exist in custom stored procedures or application queries
  3. Audit database user roles and permissions
    Run SELECT dp.name AS UserName, dp.type_desc, dr.role_name FROM sys.database_principals dp LEFT JOIN (SELECT member_principal_id, role_name FROM sys.database_role_members rm JOIN sys.database_principals rp ON rm.role_principal_id = rp.principal_id) dr ON dp.principal_id = dr.member_principal_id
    Affected if Users with elevated privileges exist alongside untrusted lower-privilege accounts that could exploit the injection
  4. Review application connection strings
    Examine application configuration files and connection strings for SQL Server authentication and check if applications run under overly privileged database logins
    Affected if Applications connect using credentials with higher privileges than necessary

Your SQL Server instance is affected if the installed version falls within any of the listed vulnerable ranges AND untrusted users have any database access that could enable them to execute SQL injection attacks.

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.6500.1 / 13.0.7095.1 / 14.0.2120.1 or later
Fixed in 13.0.6500.113.0.7095.114.0.2120.1
Interim mitigation

Mitigate by refactoring vulnerable code to use parameterized queries or stored procedures with proper input validation, applying the principle of least privilege to database accounts, and ensuring database users have only the minimum permissions required for their functions.

Recommended fix High confidence

SQL Server 2016: upgrade to 13.0.6500.1 or 13.0.7095.1; SQL Server 2017: upgrade to 14.0.2120.1 or 14.0.3540.1; SQL Server 2019: upgrade to 15.0.2180.2 or 15.0.4480.2; SQL Server 2022: upgrade to 16.0.1190.2 or 16.0.4262.2; SQL Server 2025: upgrade to 17.0.1125.2 or 17.0.4060.2

  1. 1. Identify the exact installed SQL Server version by running: SELECT @@VERSION
  2. 2. Determine which version branch your current installation falls into (2016, 2017, 2019, 2022, or 2025)
  3. 3. For SQL Server 2016: Upgrade to version 13.0.6500.1 (for builds >=13.0.6300.2) or 13.0.7095.1 (for builds >=13.0.7000.253)
  4. 4. For SQL Server 2017: Upgrade to version 14.0.2120.1 (for builds >=14.0.1000.169) or 14.0.3540.1 (for builds >=14.0.3006.16)
  5. 5. For SQL Server 2019: Upgrade to version 15.0.2180.2 (for builds >=15.0.2000.5) or 15.0.4480.2 (for builds >=15.0.4003.23)
  6. 6. For SQL Server 2022: Upgrade to version 16.0.1190.2 (for builds >=16.0.1000.6) or 16.0.4262.2 (for builds >=16.0.4003.1)
  7. 7. For SQL Server 2025: Upgrade to version 17.0.1125.2 (for builds >=17.0.1000.7) or 17.0.4060.2 (for builds >=17.0.4006.2)
  8. 8. Download the appropriate Cumulative Update (CU) or Service Pack (SP) from Microsoft Update Catalog or Microsoft Download Center
Caveat Standard SQL Server CU/SP update - minimal breaking changes expected; 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
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
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,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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