Authenticated code execution via untrusted deserialization
Published Jul 14, 2026 · Updated Jul 14, 2026
Deserialization of untrusted data in Microsoft SQL Server allows remote authenticated users to execute code through the database service. Microsoft identifies untrusted deserialization but has not disclosed the affected parser, data format, or unsafe object-instantiation path. A valid low-privilege SQL Server account and network access to the instance are required; successful exploitation executes code in the server context.
Summary
What happened
Deserialization of untrusted data in Microsoft SQL Server allows remote authenticated users to execute code through the database service. Microsoft identifies untrusted deserialization but has not disclosed the affected parser, data format, or unsafe object-instantiation path. A valid low-privilege SQL Server account and network access to the instance are required; successful exploitation executes code in the server context.
The record
- CVE
- CVE-2026-54118
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- Microsoft
- Product
- Microsoft SQL Server 2016 Service Pack 3 Azure Connect Feature Pack
- Classifications
- CWE-502, T1210
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 14, 2026CVE publishedPublication date reported by the CVE source.
- Jul 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=13.0.0 <13.0.7095.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo