CVE-2025-59250
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 · uneditedImproper input validation in JDBC Driver for SQL Server allows an unauthorized attacker to perform spoofing 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 confidenceImproper input validation in the Microsoft JDBC Driver for SQL Server allows an unauthenticated remote attacker to perform spoofing attacks. The vulnerability likely stems from insufficient validation of server responses or connection parameters, potentially enabling an attacker to impersonate the SQL Server and intercept or manipulate database communications.
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>= 10.2.0, < 10.2.4>= 11.2.0, < 11.2.4>= 12.2.0, < 12.2.1>= 12.4.0, < 12.4.3>= 12.6.0, < 12.6.5>= 12.8.0, < 12.8.2>= 12.10.0, < 12.10.2>= 13.2.0, < 13.2.1CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Microsoft JDBC Driver JAR fileSearch for JAR files containing 'mssql-jdbc' in your application dependencies, lib directories, classpath, or build artifacts. Common locations include: application lib folders, Maven/Gradle dependency folders, Docker image layers, or packaged EAR/WAR files.Affected if The mssql-jdbc driver JAR is present in your environment
-
Identify the driver versionOpen the JAR file manifest (META-INF/MANIFEST.MF) or check the filename which typically includes the version (e.g., mssql-jdbc-12.4.2.jar). You can also query the driver via code using Driver.getMajorVersion() and Driver.getMinorVersion(), or check your build configuration (pom.xml, build.gradle) for the dependency version.Affected if The driver version cannot be determined or shows an unlisted version
-
Compare installed version against affected rangesCheck if your version falls within any of these ranges: 10.2.0 to 10.2.3, 11.2.0 to 11.2.3, 12.2.0, 12.4.0 to 12.4.2, 12.6.0 to 12.6.4, 12.8.0 to 12.8.1, 12.10.0 to 12.10.1, or 13.2.0. Versions outside these ranges (including earlier versions below 10.2.0) are not affected by this specific CVE.Affected if Your driver version is within any of the affected ranges listed above
-
Verify SQL Server connectivity is in useConfirm that applications using this driver establish connections to Microsoft SQL Server or Azure SQL Database. Check connection strings, datasource configurations, or application logs for SQL Server hostnames, ports (default 1433), or SQL Server-specific connection properties.Affected if The driver connects to SQL Server; the vulnerability affects server response validation during JDBC connections
You are affected if the Microsoft JDBC Driver for SQL Server is present and its version falls within any of the listed vulnerable ranges (10.2.x, 11.2.x, 12.2.0, 12.4.x, 12.6.x, 12.8.x, 12.10.x, or 13.2.0) and the driver is used to connect to SQL Server.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.2.411.2.412.2.1
Update the Microsoft JDBC Driver for SQL Server to the latest patched version provided by Microsoft. Identify all applications using the affected driver and test the update in a staging environment before production deployment.
Upgrade to version 10.2.4, 11.2.4, 12.2.1, or 12.4.3 depending on your current version branch
- Identify the current version of Microsoft JDBC Driver for SQL Server in use by checking pom.xml, build.gradle, or the JAR file name
- Determine which version branch you are currently using (10.2.x, 11.2.x, 12.2.x, or 12.4.x)
- Upgrade to the corresponding fixed version: 10.2.4, 11.2.4, 12.2.1, or 12.4.3
- If using Maven, update the dependency version in pom.xml: <version>10.2.4</version> (or appropriate version)
- If using Gradle, update the dependency in build.gradle: implementation 'com.microsoft.sqlserver:mssql-jdbc:10.2.4'
- Replace the JAR file manually if not using a dependency manager
- Test the application to ensure the upgraded driver functions correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59250 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-59250 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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