dbcve.org
Sql Server 2016Application · Microsoft

CVE-2025-47997

MEDIUM · 5.3 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 13.0.6470.1 / 13.0.7065.1 or later.
See remediation →
59/100
Remediation priority · Elevated
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
Concurrent execution using shared resource with improper synchronization ('race condition') in SQL Server allows an authorized attacker to disclose information 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

A race condition vulnerability exists in SQL Server where concurrent execution of operations on shared resources lacks proper synchronization. This improper synchronization allows an authorized attacker to potentially disclose information by exploiting the timing window between operations.

MitigationApply the Microsoft security update for SQL Server when released. Review and implement proper locking mechanisms in custom code that accesses shared resources in SQL Server.

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.6470.1>= 13.0.7000.253, < 13.0.7065.1
Sql Server 2017Application
Affected:>= 14.0.1000.169, < 14.0.2085.1>= 14.0.3006.16, < 14.0.3505.1
Sql Server 2019Application
Affected:>= 15.0.2000.5, < 15.0.2145.1>= 15.0.4003.23, < 15.0.4445.1
Sql Server 2022Application
Affected:>= 16.0.1000.6, < 16.0.1150.1>= 16.0.4003.1, < 16.0.4212.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
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 query: SELECT SERVERPROPERTY('ProductVersion') AS BuildNumber, SERVERPROPERTY('ProductLevel') AS ServicePack, SERVERPROPERTY('Edition') AS Edition;
    Affected if The build number falls within any of these ranges: 13.0.6300.2 to 13.0.6470.1, 13.0.7000.253 to 13.0.7065.1, 14.0.1000.169 to 14.0.2085.1, 14.0.3006.16 to 14.0.3505.1, 15.0.2000.5 to 15.0.2145.1, 15.0.4003.23 to 15.0.4445.1, 16.0.1000.6 to 16.0.1150.1, or 16.0.4003.1 to 16.0.4212.1
  2. Confirm major version
    Run query: SELECT SERVERPROPERTY('ProductMajorVersion'); This returns 2016, 2017, 2019, or 2022 corresponding to the SQL Server generation.
    Affected if The major version returned is 2016, 2017, 2019, or 2022 and the build number matches the affected ranges in step 1
  3. Identify timing-sensitive workloads
    Review application code and SQL jobs that perform concurrent read/write operations on shared database objects such as shared tables, shared indexes, or global temporary objects.
    Affected if The environment runs custom code or third-party applications that perform concurrent operations on shared resources without explicit locking hints (like WITH NOLOCK, rowlock, or explicit BEGIN TRANSACTION)

Your SQL Server instance is affected if its build number falls within any of the listed vulnerable version ranges AND the instance runs concurrent operations on shared resources.

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.6470.1 / 13.0.7065.1 / 14.0.2085.1 or later
Fixed in 13.0.6470.113.0.7065.114.0.2085.1
Interim mitigation

Apply the Microsoft security update for SQL Server when released. Review and implement proper locking mechanisms in custom code that accesses shared resources in SQL Server.

Recommended fix High confidence

SQL Server 2016 to 13.0.7065.1 or later; SQL Server 2017 to 14.0.3505.1 or later; SQL Server 2019 to 15.0.4445.1 or later; SQL Server 2022 to 16.0.4212.1 or later

  1. Identify your current SQL Server version by running 'SELECT @@VERSION' in SQL Server Management Studio
  2. Determine which version branch you are on (2016, 2017, 2019, or 2022) and note your current build number
  3. For SQL Server 2016: Upgrade to build 13.0.7065.1 or later (if on Service Pack 2 branch) or 13.0.6470.1 or later (if on Service Pack 3 branch)
  4. For SQL Server 2017: Upgrade to build 14.0.3505.1 or later (if on CU30+ branch) or 14.0.2085.1 or later (if on earlier CU branch)
  5. For SQL Server 2019: Upgrade to build 15.0.4445.1 or later (if on recent branch) or 15.0.2145.1 or later (if on earlier branch)
  6. For SQL Server 2022: Upgrade to build 16.0.4212.1 or later (if on recent branch) or 16.0.1150.1 or later (if on earlier branch)
  7. Download and apply the appropriate Cumulative Update (CU) or Service Pack from the Microsoft SQL Server Release Services blog or Microsoft Update Catalog
  8. Test the update in a non-production environment before applying to production
Caveat Standard SQL Server cumulative update - minimal risk but test in non-production first; ensure backups before applying

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

Fix this in Sql Server 2016 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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