CVE-2025-47997: Microsoft SQL Server Information Disclosure Vulnerability
Published Sep 9, 2025
·Updated
Concurrent execution using shared resource with improper synchronization ('race condition') in SQL Server allows an authorized attacker to disclose information over a network.
Other sources
Microsoft SQL Server Information Disclosure Vulnerability
— Microsoft
Affected Software
16 affected componentsFixes available
Microsoft SQL Server 2022
Microsoft SQL Server 2016 Azure Connect Feature Pack
Microsoft SQL Server 2017
Microsoft SQL Server 2019
Microsoft SQL Server 2017 (CU 31)
Microsoft SQL Server 2016
Microsoft SQL Server 2016>=13.0.6300.2<13.0.6470.1
Microsoft SQL Server 2016>=13.0.7000.253<13.0.7065.1
Microsoft SQL Server 2017>=14.0.1000.169<14.0.2085.1
Microsoft SQL Server 2017>=14.0.3006.16<14.0.3505.1
Microsoft SQL Server 2019>=15.0.2000.5<15.0.2145.1
Microsoft SQL Server 2019>=15.0.4003.23<15.0.4445.1
Microsoft SQL Server 2022>=16.0.1000.6<16.0.1150.1
Microsoft SQL Server 2022>=16.0.4003.1<16.0.4212.1
Microsoft SQL Server 2019 (CU 32)
Microsoft SQL Server 2022 (CU 20)
Event History
Sep 9, 2025
CVE Published
via Microsoft·07:00 AM
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
Description
CVE Published
via MITRE·05:01 PM
Data Sourced
via MITRE·05:01 PM
DescriptionSeverity
Data Sourced
via NVD·05:15 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-47997?
CVE-2025-47997 has a medium severity rating due to its information disclosure risk.
2
How do I fix CVE-2025-47997?
To fix CVE-2025-47997, apply the appropriate security patch provided by Microsoft for your SQL Server version.
3
What versions of SQL Server are affected by CVE-2025-47997?
CVE-2025-47997 affects Microsoft SQL Server 2022, 2019, 2017, and 2016.
4
What is the impact of CVE-2025-47997?
CVE-2025-47997 allows an authorized attacker to disclose information over a network due to improper synchronization.
5
Is CVE-2025-47997 exploited in the wild?
As of now, there is no evidence that CVE-2025-47997 is actively exploited in the wild.