dbcve.org
Sql Server 2016Application · Microsoft

CVE-2026-47295

HIGH · 8.8 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 →
94/100
Remediation priority · Urgent
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 1mo 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

SQL injection vulnerability in Microsoft SQL Server allows an authenticated attacker to inject malicious SQL commands through improper input handling, potentially allowing privilege escalation from their current authorized permissions to higher-level database roles or system administrative access.

MitigationImplement parameterized queries or prepared statements for all database operations, apply principle of least privilege to database accounts, and validate/sanitize all user inputs before constructing SQL queries.

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
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. Identify SQL Server version
    Run query: SELECT @@VERSION; or check SQL Server Error Log for version entry, or open SQL Server Configuration Manager and view the SQL Server service properties
    Affected if The version matches any of the affected ranges: 2016 (13.0.6300.2 to 13.0.6500.1 or 13.0.7000.253 to 13.0.7095.1), 2017 (14.0.1000.169 to 14.0.2120.1 or 14.0.3006.16 to 14.0.3540.1), 2019 (15.0.2000.5 to 15.0.2180.2 or 15.0.4003.23 to 15.0.4480.2), 2022 (16.0.1000.6 to 16.0.1190.2 or 16.0.4003.1 to
  2. Confirm SQL Server edition and build number
    Run query: SELECT SERVERPROPERTY('Edition'), SERVERPROPERTY('ProductLevel'), SERVERPROPERTY('ProductVersion');
    Affected if ProductVersion falls within any of the vulnerable version ranges listed in the affected products
  3. Identify authenticated user privileges
    Run query: SELECT USER_NAME(), SUSER_SNAME(), IS_SRVROLEMEMBER('sysadmin'); or inspect current login permissions with: SELECT login_name, has_dbaccess, sysadmin FROM sys.syslogins WHERE loginname = SUSER_SNAME();
    Affected if The vulnerability requires an authenticated attacker; presence of any database user account indicates potential attack surface
  4. Review SQL Server authentication mode
    Run: SELECT SERVERPROPERTY('IsIntegratedSecurityOnly'); or check registry: HKLM\Software\Microsoft\Microsoft SQL Server\MSSQLServer\LoginMode
    Affected if Mixed mode authentication expands the attack surface by allowing both Windows and SQL authentication logins
  5. Audit for dynamic SQL execution patterns
    Examine application queries and stored procedures for use of EXEC(), sp_executesql, or string concatenation in queries that incorporate user input; review SQL Server Trace Flag 1222 or Extended Events for injection attempts
    Affected if Applications or procedures using unparameterized queries with user-supplied input are vulnerable to exploitation

Your SQL Server instance is affected if it runs any version within the specified ranges AND accepts authenticated database connections using dynamic SQL or unparameterized 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.

From vendor data
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

Implement parameterized queries or prepared statements for all database operations, apply principle of least privilege to database accounts, and validate/sanitize all user inputs before constructing SQL queries.

Fix this in Sql Server 2016 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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