Skip to content
Fencer Vulns
high 7.5

CVE-2025-49719 in the critical feed json

Microsoft SQL Server Information Disclosure Vulnerability

published 2025-07-08 16 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-20625

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
15.5%
EPSS 15.5% chance of exploitation in 30 days, percentile 96%
public exploits
0
none known

Summary

Improper input validation in SQL Server allows an unauthorized attacker to disclose information over a network.

Patch / fix

  • Microsoft Microsoft SQL Server 2016 for Service Pack 2 (GDR) 13.0.6460.7
  • Microsoft Microsoft SQL Server 2016 Service Pack 3 Azure Connect Feature Pack 13.0.7055.9
  • Microsoft Microsoft SQL Server 2017 (CU 31) 14.0.3495.9
  • Microsoft Microsoft SQL Server 2017 (GDR) 14.0.2075.8
  • Microsoft Microsoft SQL Server 2019 (CU 32) 15.0.4435.7
  • Microsoft Microsoft SQL Server 2019 (GDR) 15.0.2135.5
  • Microsoft Microsoft SQL Server 2022 (CU 19) 16.0.4200.1
  • Microsoft Microsoft SQL Server 2022 (GDR) 16.0.1140.6

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
16 mo ago

Exploit prediction

15.50% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected products

  • Microsoft Microsoft SQL Server 2016 for Service Pack 2 (GDR)
  • Microsoft Microsoft SQL Server 2016 Service Pack 3 Azure Connect Feature Pack
  • Microsoft Microsoft SQL Server 2017 (CU 31)
  • Microsoft Microsoft SQL Server 2017 (GDR)
  • Microsoft Microsoft SQL Server 2019 (CU 32)
  • Microsoft Microsoft SQL Server 2019 (GDR)
  • Microsoft Microsoft SQL Server 2022 (CU 19)
  • Microsoft Microsoft SQL Server 2022 (GDR)

Classification

Weakness
  • CWE-20 Improper Input Validation
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.