dbcve.org
Sql Server 2019Application · Microsoft

CVE-2025-49717

HIGH · 8.5 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 15.0.2135.5 / 15.0.4435.7 or later.
See remediation →
91/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
Heap-based buffer overflow in SQL Server allows an authorized attacker to execute code 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

Heap-based buffer overflow vulnerability in Microsoft SQL Server enabling authenticated remote attackers to execute arbitrary code via network access. The heap overflow indicates memory corruption in SQL Server's heap memory management, allowing an attacker with valid database credentials to overflow heap allocations and achieve code execution.

MitigationApply the Microsoft security update for this vulnerability once released; ensure SQL Server is updated to a patched version. Since this requires an authorized attacker, enforce least-privilege database accounts and network segmentation to limit exposure.

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 2019Application
Affected:>= 15.0.2000.5, < 15.0.2135.5>= 15.0.4003.23, < 15.0.4435.7
Sql Server 2022Application
Affected:>= 16.0.1000.6, < 16.0.1140.6>= 16.0.4003.1, < 16.0.4200.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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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 localhost -Q "SELECT @@VERSION"' from command line. Alternatively, view the installed version in Programs and Features (Windows) or check the SQL Server ERRORLOG file.
    Affected if The version number returned does not fall outside all affected ranges (15.0.2135.5+, 15.0.4435.7+, 16.0.1140.6+, 16.0.4200.1+)
  2. Confirm SQL Server edition and build number
    Run 'SELECT SERVERPROPERTY('ProductVersion'), SERVERPROPERTY('ProductLevel'), SERVERPROPERTY('Edition')' to get the precise build number and edition.
    Affected if The ProductVersion falls within any of these ranges: 15.0.2000.5 to 15.0.2134.9, 15.0.4003.23 to 15.0.4435.6, 16.0.1000.6 to 16.0.1140.5, or 16.0.4003.1 to 16.0.4200.0
  3. Verify network connectivity is enabled
    Open SQL Server Configuration Manager, navigate to SQL Server Network Configuration, and check if TCP/IP protocols are enabled. Alternatively, check if the SQL Server service is listening on port 1433 (or custom port) using 'netstat -an | findstr 1433'.
    Affected if TCP/IP protocol is enabled and SQL Server is listening on network interfaces, allowing remote connections
  4. Check for exposed SQL Server ports
    Run 'netstat -ano | findstr :1433' (or your custom SQL port) to see if SQL Server is bound to 0.0.0.0 or external IP addresses rather than only localhost.
    Affected if SQL Server is bound to non-loopback addresses (0.0.0.0 or external IP) indicating network accessibility

If the installed SQL Server version falls within any of the affected build ranges and the instance is accessible over the network, the environment is potentially affected by this heap-based buffer overflow vulnerability.

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 15.0.2135.5 / 15.0.4435.7 / 16.0.1140.6 or later
Fixed in 15.0.2135.515.0.4435.716.0.1140.6
Interim mitigation

Apply the Microsoft security update for this vulnerability once released; ensure SQL Server is updated to a patched version. Since this requires an authorized attacker, enforce least-privilege database accounts and network segmentation to limit exposure.

Recommended fix High confidence

SQL Server 2019: 15.0.2135.5 or later (CU26), or 15.0.4435.7 or later (CU31) | SQL Server 2022: 16.0.1140.6 or later (CU12), or 16.0.4200.1 or later (CU17)

  1. For SQL Server 2019: Determine current version by running 'SELECT @@VERSION' in SQL Server Management Studio
  2. If version is 15.0.2000.5 through 15.0.2135.4, upgrade to SQL Server 2019 build 15.0.2135.5 or later (Cumulative Update 26)
  3. If version is 15.0.4003.23 through 15.0.4435.6, upgrade to SQL Server 2019 build 15.0.4435.7 or later (Cumulative Update 31)
  4. For SQL Server 2022: If version is 16.0.1000.6 through 16.0.1140.5, upgrade to SQL Server 2022 build 16.0.1140.6 or later (Cumulative Update 12)
  5. If version is 16.0.4003.1 through 16.0.4200.0, upgrade to SQL Server 2022 build 16.0.4200.1 or later (Cumulative Update 17)
  6. Download the appropriate Cumulative Update from https://learn.microsoft.com/en-us/sql/database-engine/install-windows/latest-updates-for-microsoft-sql-server
  7. Apply the update during a maintenance window following standard SQL Server patching procedures
  8. Verify successful installation by running 'SELECT @@VERSION' and confirming the build number matches or exceeds the target fix version
Caveat Standard SQL Server CU update; minimal risk but test in non-production environment first as with any patch

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

Fix this in Sql Server 2019 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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