Authenticated RCE in Microsoft SQL Server; widely deployed DBMS and can lead to full server compromise across enterprises.
CVE-2026-54118
Authenticated deserialization RCE in Microsoft SQL Server allowing remote code execution.
Is CVE-2026-54118 being exploited?
Not confirmed. CVE-2026-54118 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.2% probability of exploitation in the next 30 days.
How severe is CVE-2026-54118?
CVE-2026-54118 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-54118?
Yes. A fix has been recorded for CVE-2026-54118. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-54118 affect?
CVE-2026-54118 affects Microsoft SQL Server (affected supported versions). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-54118?
Apply vendor patch immediately; restrict DB network access and enforce least privilege.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker can execute arbitrary code remotely via deserialization, leading to server takeover, data theft, or lateral movement.
Immediate action required
- affected>= 13.0.0 and < 13.0.7095.1
- affected>= 13.0.0 and < 13.0.6500.1
- affected>= 14.0.0 and < 14.0.3540.1
- affected>= 14.0.0 and < 14.0.2120.1
- affected>= 15.0.0.0 and < 15.0.4480.2
- affected>= 15.0.0 and < 15.0.2180.2
- affected>= 16.0.4260.1 and < 16.0.4262.2
- affected>= 16.0.0 and < 16.0.1190.2
- affected< 17.0.4060.2
- affected>= 17.0.1050.2 and < 17.0.1125.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.