Affects Microsoft SQL Server, a widely deployed enterprise database; privilege-escalation bug could impact many organizations and deserves broad IT notification.
CVE-2026-94513
Heap overflow in Microsoft SQL Server enabling network privilege escalation.
Is CVE-2026-94513 being exploited?
Not confirmed. CVE-2026-94513 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 0.55% probability of exploitation in the next 30 days.
How severe is CVE-2026-94513?
CVE-2026-94513 is rated High with a CVSS score of 8.0. 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-94513?
Yes. A fix has been recorded for CVE-2026-94513. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-94513 affect?
CVE-2026-94513 affects Microsoft SQL Server (unspecified versions). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-94513?
Apply Microsoft security update to all SQL Server hosts immediately; prioritize exposed/high-privilege instances.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authorized attacker can trigger a heap overflow over the network to escalate privileges on the SQL Server host, potentially gaining SYSTEM or db_owner rights.
Immediate action required
- affected>= 16.0.4003.1 and < 16.0.4315.2
- affected>= 16.0.0 and < 16.0.1220.3
- affected>= 17.0.4006.0 and < 17.0.5045.3
- affected>= 17.0.1050.2 and < 17.0.1155.3
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.
cisa ssvc
- exploitation
- none
- automatable
- no
- technical impact
- total
Assessed by CISA 11 Nov 2026 (SSVC 2.0.3).
timeline
- 10 Nov 2026Published
- 11 Nov 2026CISA SSVC assessment: exploitation none · 1 day later
- 11 Nov 2026CVE record last updated · same day later
- 12 Nov 2026Analysed by vulneraibility.com · 1 day later
- Patchmsrc.microsoft.com /update-guide/vulnerability/CVE-2026-94513
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.