Advisories
For your digest

com.microsoft.sqlserver:mssql-jdbc: JDBC Driver for SQL Server has improper input validation issue

It touches something Phylax follows. No evidence of use yet.

Does it affect what I run?

com.microsoft.sqlserver:mssql-jdbc (Maven)

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • com.microsoft.sqlserver:mssql-jdbc (Maven): from 8.3.0.jre11-preview, before 10.2.4.jre11
  • com.microsoft.sqlserver:mssql-jdbc (Maven): from 11.2.0.jre11, before 11.2.4.jre11
  • com.microsoft.sqlserver:mssql-jdbc (Maven): from 12.2.0.jre11, before 12.2.1.jre11
  • com.microsoft.sqlserver:mssql-jdbc (Maven): from 12.6.0.jre11, before 12.6.5.jre11
  • com.microsoft.sqlserver:mssql-jdbc (Maven): from 12.8.0.jre11, before 12.8.2.jre11
  • com.microsoft.sqlserver:mssql-jdbc (Maven): from 12.10.0.jre11, before 12.10.2.jre11
  • com.microsoft.sqlserver:mssql-jdbc (Maven): from 13.2.0.jre11, before 13.2.1.jre11

The fix

  • com.microsoft.sqlserver:mssql-jdbc (Maven) fixed in 10.2.4.jre11

    maven
    mvn versions:use-dep-version -Dincludes=com.microsoft.sqlserver:mssql-jdbc -DdepVersion=10.2.4.jre11 -DforceVersion=true
    Check what is installed
    mvn dependency:tree -Dincludes=com.microsoft.sqlserver:mssql-jdbc
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Maven dependency com.microsoft.sqlserver:mssql-jdbc to 10.2.4.jre11 or the nearest later release, to fix CVE-2025-59250. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • com.microsoft.sqlserver:mssql-jdbc (Maven) fixed in 11.2.4.jre11

    maven
    mvn versions:use-dep-version -Dincludes=com.microsoft.sqlserver:mssql-jdbc -DdepVersion=11.2.4.jre11 -DforceVersion=true
    Check what is installed
    mvn dependency:tree -Dincludes=com.microsoft.sqlserver:mssql-jdbc
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Maven dependency com.microsoft.sqlserver:mssql-jdbc to 11.2.4.jre11 or the nearest later release, to fix CVE-2025-59250. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • com.microsoft.sqlserver:mssql-jdbc (Maven) fixed in 12.2.1.jre11

    maven
    mvn versions:use-dep-version -Dincludes=com.microsoft.sqlserver:mssql-jdbc -DdepVersion=12.2.1.jre11 -DforceVersion=true
    Check what is installed
    mvn dependency:tree -Dincludes=com.microsoft.sqlserver:mssql-jdbc
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Maven dependency com.microsoft.sqlserver:mssql-jdbc to 12.2.1.jre11 or the nearest later release, to fix CVE-2025-59250. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • com.microsoft.sqlserver:mssql-jdbc (Maven) fixed in 12.6.5.jre11

    maven
    mvn versions:use-dep-version -Dincludes=com.microsoft.sqlserver:mssql-jdbc -DdepVersion=12.6.5.jre11 -DforceVersion=true
    Check what is installed
    mvn dependency:tree -Dincludes=com.microsoft.sqlserver:mssql-jdbc
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Maven dependency com.microsoft.sqlserver:mssql-jdbc to 12.6.5.jre11 or the nearest later release, to fix CVE-2025-59250. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • com.microsoft.sqlserver:mssql-jdbc (Maven) fixed in 12.8.2.jre11

    maven
    mvn versions:use-dep-version -Dincludes=com.microsoft.sqlserver:mssql-jdbc -DdepVersion=12.8.2.jre11 -DforceVersion=true
    Check what is installed
    mvn dependency:tree -Dincludes=com.microsoft.sqlserver:mssql-jdbc
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Maven dependency com.microsoft.sqlserver:mssql-jdbc to 12.8.2.jre11 or the nearest later release, to fix CVE-2025-59250. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • com.microsoft.sqlserver:mssql-jdbc (Maven) fixed in 12.10.2.jre11

    maven
    mvn versions:use-dep-version -Dincludes=com.microsoft.sqlserver:mssql-jdbc -DdepVersion=12.10.2.jre11 -DforceVersion=true
    Check what is installed
    mvn dependency:tree -Dincludes=com.microsoft.sqlserver:mssql-jdbc
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Maven dependency com.microsoft.sqlserver:mssql-jdbc to 12.10.2.jre11 or the nearest later release, to fix CVE-2025-59250. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • com.microsoft.sqlserver:mssql-jdbc (Maven) fixed in 13.2.1.jre11

    maven
    mvn versions:use-dep-version -Dincludes=com.microsoft.sqlserver:mssql-jdbc -DdepVersion=13.2.1.jre11 -DforceVersion=true
    Check what is installed
    mvn dependency:tree -Dincludes=com.microsoft.sqlserver:mssql-jdbc
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Maven dependency com.microsoft.sqlserver:mssql-jdbc to 13.2.1.jre11 or the nearest later release, to fix CVE-2025-59250. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.

Fix commands generated from the advisory's versions. No model wrote them.

In plain words

Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.

Evidence

No evidence that it is being used, or can be. It is listed because of what it affects.

Timeline

  1. First published here, as "For your digest".