External risk intelligence

SQL Server Untrusted Data Deserialization Allows Network Code Execution.

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-54118

SQL Server is a database management system that is typically deployed within internal network segments or behind firewalls to support applications. While network-reachable in some environments, public internet exposure is an uncommon configuration for this type of product, as it is generally intended for backend service rather than direct public access.

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability in Microsoft SQL Server could allow attackers to execute malicious code remotely by exploiting how the server handles untrusted data. This could potentially lead to unauthorized access and control over affected database systems. The primary concern is to confirm whether our SQL Server deployments are exposed and vulnerable.

  • Untrusted data handling in SQL Server can be exploited.
  • Critical vulnerability allows remote code execution.
  • Confirm exposure and relevance to our systems.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by sending specially crafted data over the network to a vulnerable SQL Server instance. This untrusted data is then deserialized, allowing the attacker to execute arbitrary code remotely, which could lead to a complete compromise of the server.

  • No special access required.
  • Triggers via deserializing untrusted data.
  • Leads to remote code execution.

Live Threat

Current exploitation, exposure, and threat context

When SQL Server deserializes untrusted data, an unauthorized attacker could execute code over a network. This could impact the integrity and availability of the SQL Server instance and any data it manages.

  • SQL Server instance and managed data.
  • Network access with no user interaction.
  • Compromised server and data integrity.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts SQL Server, a critical database component typically managed by infrastructure or platform teams. The initial focus should be on identifying all SQL Server instances, assessing their network exposure and business criticality, and locating the accountable system owner. Remediation planning should then proceed based on this risk assessment.

  • Infrastructure or platform teams own remediation.
  • Verify network reachability and business criticality.
  • Plan remediation based on identified risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Microsoft SQL Server software affected by CVE-2026-54118?

SQL Server is a database management system used to store and retrieve data as requested by other software applications. It serves as a backend component for various enterprise tools, handling large volumes of information and ensuring data consistency. The versions listed in the catalog, ranging from 2016 through 2025, are affected by this issue when running within specific build ranges.

How does this deserialization vulnerability work?

This vulnerability is classified as CWE-502, which concerns the deserialization of untrusted data. When the software takes data from an external source and converts it back into an object without sufficient validation, it can unintentionally follow malicious instructions embedded in that data. In this specific case, the flaw allows an attacker to execute their own arbitrary code on the database server.

What is required to trigger this vulnerability?

An attacker needs network access to the target SQL Server instance to send specially crafted data that the server then deserializes. The trigger does not require the attacker to have existing privileges or accounts on the system, nor does it require any interaction from a legitimate user. Simply reaching the service over the network with the malicious payload is sufficient to initiate the flaw.

Is my SQL Server at risk if it is behind a firewall?

According to Halo Surface Signal, this software is typically deployed in internal network segments rather than on the public internet. While the vulnerability is network-reachable, its practical risk often depends on whether your instance is exposed to untrusted zones. If the database is tucked behind a firewall and isolated from public access, the immediate likelihood of an external attack is lower compared to systems directly connected to the internet.

How should I respond to this threat?

Start by identifying all instances of SQL Server within your environment and mapping them to their respective system owners. Review the affected build numbers provided in the advisory to determine which specific servers are running vulnerable versions. Once you have a clear inventory, prioritize your remediation planning by evaluating the business criticality and network reachability of each identified instance.

References