LiveActive security incident?Get immediate response
CVE Record

CVE-2026-54118: Microsoft SQL Server Remote Code Execution Vulnerability

Deserialization of untrusted data in SQL Server allows an authorized attacker to execute code over a network.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A user with limited authorized access to a vulnerable Microsoft SQL Server could exploit unsafe data handling to run code remotely. Successful exploitation could expose, alter, or disrupt databases and the underlying server. No user interaction is required, making reachable systems with broadly issued credentials the main concern.

Executive priority

Treat as a high-priority patching cycle, especially for business-critical or broadly reachable SQL Server systems. The prerequisite for authorized access prevents a critical rating, but compromised credentials could convert this flaw into full server and database impact. Track inventory, update completion, and exceptions to closure.

Technical view

CVE-2026-54118 is a CWE-502 deserialization flaw in affected SQL Server releases. It is network-accessible, low complexity, and requires low privileges but no user interaction. Microsoft rates it CVSS 3.1 8.8, with potentially high confidentiality, integrity, and availability impact.

Likely exposure

Exposure exists where listed SQL Server 2016, 2017, 2019, 2022, or 2025 branches are deployed and reachable by authorized low-privilege users. The supplied version identifiers do not establish complete vulnerable build ranges; confirm each installed build against Microsoft’s advisory.

Exploitation context

The supplied record does not report active exploitation, and the CVE is not identified as CISA KEV. Exploitation requires authorized access, reducing anonymous risk but leaving insider, compromised-account, and application-credential scenarios relevant. Public exploit availability is not established by the provided sources.

Researcher notes

The record supports network code execution through untrusted-data deserialization with low privileges. It does not describe the vulnerable protocol, component, payload format, complete build boundaries, indicators of compromise, or observed exploitation. Researchers and defenders should rely on Microsoft’s advisory for precise update applicability and avoid inferring affected builds from major-version identifiers alone.

Mitigation direction

  • Review Microsoft’s advisory and install the applicable security update for each affected SQL Server deployment.
  • Prioritize network-reachable production, identity, financial, and customer-data database servers.
  • Restrict SQL Server network access to required applications, administrators, and trusted management paths.
  • Review and reduce low-privilege accounts, shared credentials, and unnecessary application access.
  • Maintain tested database and system backups before remediation.

Validation and detection

  • Inventory SQL Server versions, editions, servicing branches, and exact installed build numbers.
  • Compare each build with Microsoft’s affected-products and security-update information.
  • Confirm the applicable update installed successfully and survives service restart.
  • Test required applications and database connectivity after updating.
  • Review access paths and accounts capable of reaching each affected instance.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-54118 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C2.85.9microsoft

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-54118Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftMicrosoft SQL Server 2016 Service Pack 3 (GDR)13.0.0Listed
MicrosoftMicrosoft SQL Server 2016 Service Pack 3 Azure Connect Feature Pack13.0.0Listed
MicrosoftMicrosoft SQL Server 2017 (CU 31)14.0.0Listed
MicrosoftMicrosoft SQL Server 2017 (GDR)14.0.0Listed
MicrosoftMicrosoft SQL Server 2019 (CU 32)15.0.0.0Listed
MicrosoftMicrosoft SQL Server 2019 (GDR)15.0.0Listed
MicrosoftMicrosoft SQL Server 2022 (GDR)16.0.0Listed
MicrosoftMicrosoft SQL Server 2022 for x64-based Systems (CU 25)16.0.4260.1Listed
MicrosoftMicrosoft SQL Server 2025 (CU 6)17.0.4060.2Listed
MicrosoftMicrosoft SQL Server 2025 for x64-based Systems (GDR)17.0.1050.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.