Quick answers
- Is CVE-2026-54117 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54117 being exploited in the wild.
- How severe is CVE-2026-54117?
- High severity, with a CVSS score of 8.8, 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-54117?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-54117 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-54117?
- 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 deserialization vulnerability (CWE-502) exists in Microsoft SQL Server 2025. The flaw is rooted in the way the server processes untrusted data during deserialization operations, which can be manipulated to trigger arbitrary code execution. An attacker must be authenticated to the network and have basic permissions (Low Privileges) to reach the vulnerable component. Successful exploitation allows for remote code execution (RCE) in the context of the SQL Server service account, potentially leading to full system compromise. 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: disclosed
- 2026-07-14: advisory