# CVE-2025-59250: JDBC Driver for SQL Server Spoofing Vulnerability > An unauthorized attacker can perform spoofing over the network due to improper input validation in the Microsoft JDBC Driver for SQL Server. - **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 14 Oct 2025 - **Updated:** 26 Feb 2026 - **Also known as:** CLEANSTART-2026-IW64102, CLEANSTART-2026-MW74031, CLEANSTART-2026-ZC26569, ECHO-d399-babc-bf30, GHSA-m494-w24q-6f7w, MINI-c8qq-8q7w-xpg9, MINI-h943-qqch-hv86, MINI-m2r4-x8jg-mrjp, ROOT-APP-MAVEN-CVE-2025-59250 ## What is CVE-2025-59250? CVE-2025-59250 is a high-severity vulnerability in Microsoft JDBC Driver for SQL Server 10.2, published on 14 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Improper input validation in JDBC Driver for SQL Server allows an unauthorized attacker to perform spoofing over a network. Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2025-59250? 14 open source packages ship an affected version, including com.microsoft.sqlserver:mssql-jdbc. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `com.microsoft.sqlserver:mssql-jdbc` | Maven | From 11.2.0.jre11 | 11.2.4.jre11 | | `com.microsoft.sqlserver:mssql-jdbc` | Maven | From 11.2.0.jre11 | 11.2.4.jre11 | | `com.microsoft.sqlserver:mssql-jdbc` | Maven | From 12.10.0.jre11 | 12.10.2.jre11 | | `com.microsoft.sqlserver:mssql-jdbc` | Maven | From 12.10.0.jre11 | 12.10.2.jre11 | | `com.microsoft.sqlserver:mssql-jdbc` | Maven | From 12.2.0.jre11 | 12.2.1.jre11 | | `com.microsoft.sqlserver:mssql-jdbc` | Maven | From 12.2.0.jre11 | 12.2.1.jre11 | | `com.microsoft.sqlserver:mssql-jdbc` | Maven | From 12.6.0.jre11 | 12.6.5.jre11 | | `com.microsoft.sqlserver:mssql-jdbc` | Maven | From 12.6.0.jre11 | 12.6.5.jre11 | | `com.microsoft.sqlserver:mssql-jdbc` | Maven | From 12.8.0.jre11 | 12.8.2.jre11 | | `com.microsoft.sqlserver:mssql-jdbc` | Maven | From 12.8.0.jre11 | 12.8.2.jre11 | | `com.microsoft.sqlserver:mssql-jdbc` | Maven | From 13.2.0.jre11 | 13.2.1.jre11 | | `com.microsoft.sqlserver:mssql-jdbc` | Maven | From 13.2.0.jre11 | 13.2.1.jre11 | | `com.microsoft.sqlserver:mssql-jdbc` | Maven | From 8.3.0.jre11-preview | 10.2.4.jre11 | | `com.microsoft.sqlserver:mssql-jdbc` | Maven | From 8.3.0.jre11-preview | 10.2.4.jre11 | Products: Microsoft Jdbc Driver for Sql Server. ## How do I fix CVE-2025-59250? Upgrade com.microsoft.sqlserver:mssql-jdbc to a fixed version for your release line: 11.2.4.jre11, 12.10.2.jre11, 12.2.1.jre11 or 12.6.5.jre11. ## Is CVE-2025-59250 being exploited? There is no known exploitation of CVE-2025-59250 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-59250 and fix it if it is affected. What it is: CVE-2025-59250 is a high-severity vulnerability in Microsoft JDBC Driver for SQL Server 10.2, published on 14 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2025-59250 in the wild and no public exploit code. Affected packages and fixed versions: - com.microsoft.sqlserver:mssql-jdbc (Maven): affected from 11.2.0.jre11; fixed in 11.2.4.jre11 - com.microsoft.sqlserver:mssql-jdbc (Maven): affected from 11.2.0.jre11; fixed in 11.2.4.jre11 - com.microsoft.sqlserver:mssql-jdbc (Maven): affected from 12.10.0.jre11; fixed in 12.10.2.jre11 - com.microsoft.sqlserver:mssql-jdbc (Maven): affected from 12.10.0.jre11; fixed in 12.10.2.jre11 - com.microsoft.sqlserver:mssql-jdbc (Maven): affected from 12.2.0.jre11; fixed in 12.2.1.jre11 - com.microsoft.sqlserver:mssql-jdbc (Maven): affected from 12.2.0.jre11; fixed in 12.2.1.jre11 - com.microsoft.sqlserver:mssql-jdbc (Maven): affected from 12.6.0.jre11; fixed in 12.6.5.jre11 - com.microsoft.sqlserver:mssql-jdbc (Maven): affected from 12.6.0.jre11; fixed in 12.6.5.jre11 - com.microsoft.sqlserver:mssql-jdbc (Maven): affected from 12.8.0.jre11; fixed in 12.8.2.jre11 - com.microsoft.sqlserver:mssql-jdbc (Maven): affected from 12.8.0.jre11; fixed in 12.8.2.jre11 - com.microsoft.sqlserver:mssql-jdbc (Maven): affected from 13.2.0.jre11; fixed in 13.2.1.jre11 - com.microsoft.sqlserver:mssql-jdbc (Maven): affected from 13.2.0.jre11; fixed in 13.2.1.jre11 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-59250/ (Markdown: https://insights.sbomify.com/CVE-2025-59250/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59250 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59250 - OSV: https://osv.dev/vulnerability/CVE-2025-59250 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-59250/ Summaries are generated and may contain mistakes; the official description above is the record.