Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.1

JDBC Driver for SQL Server has improper input validation issue

CVE-2025-59250GHSA-m494-w24q-6f7w

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (com.microsoft.sqlserver:mssql-jdbc 13.2.1.jre11, 12.10.2.jre11, 12.8.2.jre11, 12.6.5.jre11, 12.2.1.jre11, 11.2.4.jre11, 10.2.4.jre11), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Maven com.microsoft.sqlserver:mssql-jdbc

    Affected
    >= 11.2.0.jre11, < 11.2.4.jre11>= 12.2.0.jre11, < 12.2.1.jre11>= 12.6.0.jre11, < 12.6.5.jre11>= 12.8.0.jre11, < 12.8.2.jre11>= 12.10.0.jre11, < 12.10.2.jre11>= 13.2.0.jre11, < 13.2.1.jre11>= 8.3.0.jre11-preview, < 10.2.4.jre11
    Fixed in
    12.2.1.jre11, 12.8.2.jre11, 10.2.4.jre11, 12.6.5.jre11, 11.2.4.jre11, 12.10.2.jre11, 13.2.1.jre11

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-m494-w24q-6f7w lists affected ranges: Maven com.microsoft.sqlserver:mssql-jdbc >=11.2.0.jre11 =12.2.0.jre11 =12.6.0.jre11 =12.8.0.jre11 =12.10.0.jre11 =13.2.0.jre11 =8.3.0.jre11-preview <10.2.4.jre11

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
EPSS
  • CVE-2025-59250: 0.73% estimated exploitation activity in the next 30 days; percentile 54.48 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Improper input validation in JDBC Driver for SQL Server allows an unauthorized attacker to perform spoofing over a network.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-m494-w24q-6f7w

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-59250

Advisory: JDBC Driver for SQL Server has improper input validation issue
IDs: CVE-2025-59250, GHSA-m494-w24q-6f7w
Record: https://patchnext.com/advisories/cve-2025-59250 (revision 1, source checked 26 Oct 2026, 16:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.microsoft.sqlserver:mssql-jdbc 13.2.1.jre11, 12.10.2.jre11, 12.8.2.jre11, 12.6.5.jre11, 12.2.1.jre11, 11.2.4.jre11, 10.2.4.jre11. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.microsoft.sqlserver:mssql-jdbc: affected >= 11.2.0.jre11, < 11.2.4.jre11; >= 12.2.0.jre11, < 12.2.1.jre11; >= 12.6.0.jre11, < 12.6.5.jre11; >= 12.8.0.jre11, < 12.8.2.jre11; >= 12.10.0.jre11, < 12.10.2.jre11; >= 13.2.0.jre11, < 13.2.1.jre11; >= 8.3.0.jre11-preview, < 10.2.4.jre11; fixed in 12.2.1.jre11, 12.8.2.jre11, 10.2.4.jre11, 12.6.5.jre11, 11.2.4.jre11, 12.10.2.jre11, 13.2.1.jre11

## Suggested inspection (read-only)
- Maven com.microsoft.sqlserver:mssql-jdbc: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.microsoft.sqlserver:mssql-jdbc.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-m494-w24q-6f7w (GitHub-reviewed advisory GHSA-m494-w24q-6f7w lists affected ranges: Maven com.microsoft.sqlserver:mssql-jdbc >=11.2.0.jre11 =12.2.0.jre11 =12.6.0.jre11 =12.8.0.jre11 =12.10.0.jre11 =13.2.0.jre11 =8.3.0.jre11-preview <10.2.4.jre11)

Commands are suggestions: review each one before running it.

Loading voting…