Quick answers
- Is CVE-2026-54116 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54116 being exploited in the wild.
- How severe is CVE-2026-54116?
- Medium severity, with a CVSS score of 6.5, published 14 July 2026.
- Which products and versions are affected?
- Microsoft Sql Server 2025 17.0.4060.2.
- Is there a fix for CVE-2026-54116?
- A patch was published on 2026-07-14: Security updates made available via MSRC update guide Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54116 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-54116?
- Check whether you run Microsoft Sql Server 2025 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A type confusion vulnerability (CWE-843) exists in Microsoft SQL Server 2025. The flaw occurs when the application accesses a resource using an incompatible type, which can be triggered by a remote attacker with low-level privileges (PR:L). Successful exploitation allows the attacker to disclose sensitive information over the network, though it does not grant the ability to modify data or cause a denial of service. The vulnerability affects SQL Server 2025 CU 6 and specific GDR versions for x64-based systems. Microsoft has released security updates to address this issue.
Affected products
- Microsoft SQL Server 2025 (CU 6) 17.0.4060.2
- Microsoft SQL Server 2025 for x64-based Systems (GDR) 17.0.1050.2 to 17.0.1125.2
Timeline
- 2026-07-14: advisory: Initial publication by Microsoft and NVD
- 2026-07-14: patched: Security updates made available via MSRC update guide