CVE-2026-54118 is a high-severity remote code execution vulnerability in Microsoft SQL Server caused by deserialization of untrusted data. The flaw allows an authorized attacker to send crafted data to a vulnerable SQL Server instance over the network and achieve code execution without user interaction. Microsoft rates the issue with CVSS v3.1 8.8 and indicates high impact to confidentiality, integrity, and availability. Affected product lines include supported releases of SQL Server 2016, 2017, 2019, 2022, and 2025 prior to the patched builds published in July 2026.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical remote code execution vulnerability in Microsoft SQL Server.
A SQL Server remote code execution vulnerability mentioned in the monthly patch summary.
A high-severity remote code execution vulnerability in Microsoft SQL Server caused by deserialization of untrusted data (CWE-502), allowing an authorized attacker to execute code over a network.
A critical remote code execution vulnerability in Microsoft SQL Server.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.