dbcve.org
Sql Server 2019Application · Microsoft

CVE-2025-49718

HIGH · 7.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 →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Use of uninitialized resource in SQL Server allows an unauthorized 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

This is a memory disclosure vulnerability in Microsoft SQL Server where an uninitialized resource (likely memory) is used during processing, allowing an unauthenticated remote attacker to gain access to sensitive information by sending specially crafted network requests to the SQL Server instance.

MitigationApply the latest Microsoft SQL Server security updates or patches that address this vulnerability. Review SQL Server access controls and network exposure to limit attack surface.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify SQL Server version
    Run the query 'SELECT @@VERSION' in SQL Server Management Studio or execute 'sqlcmd -S <server> -Q "SELECT @@VERSION"' from a command prompt
    Affected if The version returned falls within any of these ranges: 15.0.2000.5 to 15.0.2135.4, 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
  2. Verify SQL Server instance is network accessible
    Check if TCP/IP or Named Pipes protocols are enabled in SQL Server Configuration Manager under 'SQL Server Network Configuration', and review firewall rules or network ACLs allowing inbound connections to port 1433 (default)
    Affected if The SQL Server instance accepts remote network connections from untrusted networks or the internet
  3. Confirm remote connections are enabled
    Execute 'EXEC sp_configure ''remote access''' or check the server properties in SQL Server Management Studio under 'Connections' settings
    Affected if Remote connections are enabled and the instance is listening on network interfaces accessible to attackers

You are affected if your SQL Server version is within the vulnerable version ranges AND the instance is network accessible to unauthenticated remote attackers.

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 latest Microsoft SQL Server security updates or patches that address this vulnerability. Review SQL Server access controls and network exposure to limit attack surface.

Recommended fix High confidence

SQL Server 2019: CU27 (15.0.4435.7) or later; SQL Server 2022: CU14 (16.0.4200.1) or later

  1. Identify your current SQL Server version by running: SELECT @@VERSION
  2. For SQL Server 2019: Upgrade to Cumulative Update 27 (build 15.0.4435.7) or later
  3. For SQL Server 2022: Upgrade to Cumulative Update 14 (build 16.0.4200.1) or later
  4. Download the appropriate update from the Microsoft Security Response Center (msrc.microsoft.com) or Microsoft Update Catalog
  5. Apply the update during a planned maintenance window following standard SQL Server patching procedures
  6. Restart the SQL Server service as required by the update
  7. Verify the version after patching: SELECT @@VERSION
Caveat Standard SQL Server update - review release notes for any deprecated features or behavior changes in the target CU

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

Fix this in Sql Server 2019 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,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 $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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