Quick answers
- Is CVE-2026-50468 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-50468 being exploited in the wild.
- How severe is CVE-2026-50468?
- 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-50468?
- 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-50468 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-50468?
- 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 buffer over-read vulnerability (CWE-126) exists in Microsoft SQL Server 2025. The flaw is triggered when the application reads beyond the end of an intended buffer, allowing an attacker to access adjacent memory contents. An attacker must be authenticated to the SQL Server instance (Low Privileges) to exploit this vulnerability over the network. Successful exploitation results in unauthorized information disclosure, though it does not provide a mechanism for data modification or service disruption. Microsoft has released security updates to address this issue across affected versions.
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