🛡️ CVE-2025-59250 — jdbc-driver-for-sql-server

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. A user must be tricked into taking some action. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability none.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

• Attack vector: Network — reachable from anywhere that can route to the service.
• Attack complexity: Low — the attack works reliably, with no preparation.
• Privileges required: None — an unauthenticated stranger can try it.
• User interaction: Required — someone has to click, open or visit something.
• Scope: Unchanged — the damage stays inside the vulnerable component.
• Confidentiality impact: High — total loss, or loss the attacker controls.
• Integrity impact: High — total loss, or loss the attacker controls.
• Availability impact: None.

Weakness class

CVE-2025-59250 is classified as CWE-20: Improper Input Validation. The application accepts input without checking that it has the expected form, so malformed values reach code that assumes they are well formed.

Affected software

CVE-2025-59250 is recorded against 2 packages.

• com.microsoft.sqlserver:mssql-jdbc (from 13.2.0.jre11 up to 13.2.1.jre11)
• jdbc-driver-for-sql-server (from 13.2.0 up to 13.2.1)

Timeline and source

Published on 14 October 2025 and last revised on 4 February 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

nvd.nist.gov (Advisory)
github.com (Web)
github.com (Web)
github.com (Web)
github.com (Web)
github.com (Web)
github.com (Web)
github.com (Web)
github.com (Package)
github.com (Web)
learn.microsoft.com (Web)
msrc.microsoft.com (Web)

Same weakness in other software

These advisories are the same class of weakness (CWE-20: Improper Input Validation) in other software:

• CVE-2022-29201 (5.0 Medium, published 9 Jul 2026)
• CVE-2022-29192 (5.0 Medium, published 9 Jul 2026)
• CVE-2016-1517 (published 9 Jul 2026)
• CVE-2022-29213 (5.0 Medium, published 9 Jul 2026)
• CVE-2022-29191 (5.0 Medium, published 9 Jul 2026)
• CVE-2022-29212 (5.0 Medium, published 9 Jul 2026)
• CVE-2022-29211 (5.0 Medium, published 9 Jul 2026)
• CVE-2022-29207 (5.0 Medium, published 9 Jul 2026)

Details

Affected Packages

References