NVD / CVE Program· CNA microsoft

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

CriticalCVSS 9.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 39/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.5% (FIRST EPSS); higher than 75.1% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Microsoft SQL Server 2025 for x64-based Systems (CU6) 17.0.4060.2; Microsoft SQL Server 2025 for x64-based Systems (GDR) 17.0.1125.2.

Low priority for now. Upgrade to Microsoft SQL Server 2025 for x64-based Systems (CU6) 17.0.4060.2; Microsoft SQL Server 2025 for x64-based Systems (GDR) 17.0.1125.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

EUVD-2026-44031

Published: Jul 14, 2026
Updated: Nov 10, 2026
EPSS: 1.5% · 75th percentile
CWE: CWE-502

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.5%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 9.8
CNA · microsoft: 9.8; agree

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
microsoft	sql server 2016	cpe:2.3:a:microsoft:sql_server_2016
microsoft	sql server 2017	cpe:2.3:a:microsoft:sql_server_2017
microsoft	sql server 2019	cpe:2.3:a:microsoft:sql_server_2019
microsoft	sql server 2022	cpe:2.3:a:microsoft:sql_server_2022
microsoft	sql server 2025	cpe:2.3:a:microsoft:sql_server_2025

Versions reported by the vendor

Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.

Microsoft Microsoft SQL Server 2025 (CU 6)
- 17.0.4060.2 and later · before 17.0.4060.2affected
Microsoft Microsoft SQL Server 2025 for x64-based Systems (GDR)
- 17.0.1050.2 and later · before 17.0.1125.2affected

Affected versions · NVD (10)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

microsoft sql server 201613.0.6300.2 and later · before 13.0.6500.1
microsoft sql server 201613.0.7000.253 and later · before 13.0.7095.1
microsoft sql server 201714.0.1000.169 and later · before 14.0.2120.1
microsoft sql server 201714.0.3006.16 and later · before 14.0.3540.1
microsoft sql server 201915.0.2000.5 and later · before 15.0.2180.2
microsoft sql server 201915.0.4003.23 and later · before 15.0.4480.2
microsoft sql server 202216.0.1000.6 and later · before 16.0.1190.2
microsoft sql server 202216.0.4003.1 and later · before 16.0.4262.2
microsoft sql server 202517.0.1000.7 and later · before 17.0.1125.2
microsoft sql server 202517.0.4006.2 and later · before 17.0.4060.2

Same product

microsoft: all records

Other highest-scoring records for the same primary product.

CVE-2026-54118Microsoft SQL Server Remote Code Execution Vulnerability
39Monitor
CVE-2024-37980Microsoft SQL Server Elevation of Privilege Vulnerability
39Monitor
CVE-2025-24999Microsoft SQL Server Elevation of Privilege Vulnerability
36Monitor

Published before and after this one in the same product

← EarlierCVE-2026-40370May 12, 2026 · SQL Server Remote Code Execution Vulnerability
35Monitor
← EarlierCVE-2026-47296Jul 14, 2026 · Microsoft SQL Server Elevation of Privilege Vulnerability
30Monitor
Later →CVE-2026-55002Jul 14, 2026 · Microsoft SQL Server Elevation of Privilege Vulnerability
35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Microsoft SQL Server 2025 for x64-based Systems (CU6)	17.0.4060.2 · KB5101346	Microsoft (MSRC)
Microsoft SQL Server 2025 for x64-based Systems (GDR)	17.0.1125.2 · KB5102333	Microsoft (MSRC)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-541180 days apartMicrosoft SQL Server Remote Code Execution Vulnerability
39Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-502 · Deserialization of Untrusted Data

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.

The bug in code

The whole CWE-502 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

python

1payload = sock.recv(65536)
2job = pickle.loads(payload)

Fixed

python

1payload = sock.recv(65536)
2if not hmac.compare_digest(sign(payload), header_sig):
3    raise PermissionError("invalid signature")
4job = JobSchema.validate(json.loads(payload))

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

Object InjectionCAPEC-586likelihood: Medium · High

ATT&CK techniques

—

Change log (1)

Fix✗ → ✓Sep 30, 2026, 3:32 AM UTC

For records you follow, these changes also arrive as notifications. →

References

msrc.microsoft.com/update-guide/vulnerability/CVE-2026-54117

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records