Skip to content
Noroxi
CVE-2026-68883· CVE.org (no NVD analysis yet)· CNA microsoft

Microsoft SQL Server Elevation of Privilege Vulnerability

Noroxi assessment

Priority: Monitor (action score 34/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: 0.38% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Microsoft SQL Server 2017 for x64-based Systems (CU31) 14.0.3560.2; Microsoft SQL Server 2017 for x64-based Systems (GDR) 14.0.2140.2; Microsoft SQL Server 2019 for x64-based Systems (CU32) 15.0.4500.2.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Microsoft SQL Server 2017 for x64-based Systems (CU31) 14.0.3560.2; Microsoft SQL Server 2017 for x64-based Systems (GDR) 14.0.2140.2; Microsoft SQL Server 2019 for x64-based Systems (CU32) 15.0.4500.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

Heap-based buffer overflow in SQL Server allows an authorized attacker to elevate privileges over a network.

HighCVSS 8.5 · v3.1—No exploit Fix available
Published
Oct 13, 2026
Updated
Oct 23, 2026
EPSS
0.3% · 31th percentile

Report tools

JSON

Action score

34

Monitor

Low priority for now.

CVSS
34 / 40 · 8.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · microsoft
8.5
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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.

Follow CVE-2026-68883

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

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.

—

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 2017 (GDR)

    • 14.0.0 and later · before 14.0.2140.2affected
  • Microsoft Microsoft SQL Server 2017 for x64-based Systems (CU31)

    • 14.0.3006.16 and later · before 14.0.3560.2affected
  • Microsoft Microsoft SQL Server 2019 (GDR)

    • 15.0.0 and later · before 15.0.2200.2affected
  • Microsoft Microsoft SQL Server 2019 for x64-based Systems (CU32)

    • 15.0.4003.23 and later · before 15.0.4500.2affected
  • Microsoft Microsoft SQL Server 2022 (GDR)

    • 16.0.0 and later · before 16.0.1210.3affected
  • Microsoft Microsoft SQL Server 2022 for x64-based Systems (CU27)

    • 16.0.4003.1 and later · before 16.0.4305.5affected
  • Microsoft Microsoft SQL Server 2025 (CU8)

    • -affected
  • Microsoft Microsoft SQL Server 2025 for x64-based Systems (CU9)

    • 17.0.4006.2 and later · before 17.0.5015.4affected
  • Microsoft Microsoft SQL Server 2025 for x64-based Systems (GDR)

    • 17.0.1050.2 and later · before 17.0.1145.4affected

Other highest-scoring records for the same primary product.

  • CVE-2026-94512SQL Server Remote Code Execution Vulnerability
    35Monitor
  • CVE-2026-85886Microsoft SQL Server Remote Code Execution Vulnerability
    34Monitor
  • CVE-2026-67625Microsoft SQL Server Remote Code Execution Vulnerability
    34Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-67628Oct 13, 2026 · Microsoft SQL Server Information Disclosure Vulnerability
    19Monitor
  • Later →CVE-2026-70189Oct 13, 2026 · Microsoft SQL Server Remote Code Execution Vulnerability
    26Monitor
  • Later →CVE-2026-85888Oct 13, 2026 · Microsoft SQL Server Information Disclosure Vulnerability
    30Monitor

Remediation

Which version to upgrade to

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

Product / packageFixed versionSource
Microsoft SQL Server 2017 for x64-based Systems (CU31)14.0.3560.2 · KB5128496Microsoft (MSRC)
Microsoft SQL Server 2017 for x64-based Systems (GDR)14.0.2140.2 · KB5128497Microsoft (MSRC)
Microsoft SQL Server 2019 for x64-based Systems (CU32)15.0.4500.2 · KB5128494Microsoft (MSRC)
Microsoft SQL Server 2019 for x64-based Systems (GDR)15.0.2200.2 · KB5128495Microsoft (MSRC)
Microsoft SQL Server 2022 for x64-based Systems (CU27)16.0.4305.5 · KB5126934Microsoft (MSRC)
Microsoft SQL Server 2022 for x64-based Systems (GDR)16.0.1210.3 · KB5128493Microsoft (MSRC)
Microsoft SQL Server 2025 for x64-based Systems (CU9)17.0.5015.4 · KB5126967Microsoft (MSRC)
Microsoft SQL Server 2025 for x64-based Systems (GDR)17.0.1145.4 · KB5128492Microsoft (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.

  1. Published
  2. Fix recordedsame day
  3. TodayOct 23, 2026+10 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

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

  • CVE-2026-945120 days apartSQL Server Remote Code Execution Vulnerability
    35Monitor
  • CVE-2026-676250 days apartMicrosoft SQL Server Remote Code Execution Vulnerability
    34Monitor
  • CVE-2026-858860 days apartMicrosoft SQL Server Remote Code Execution Vulnerability
    34Monitor
  • CVE-2026-701890 days apartMicrosoft SQL Server Remote Code Execution Vulnerability
    26Monitor
  • CVE-2026-880850 days apartMicrosoft SQL Server Elevation of Privilege Vulnerability
    25Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

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

Impact can extend beyond the vulnerable component (scope changes).

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

CVSS vector

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

nvd-secondary

Attack context

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

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓
  2. SSVC exploitation— → none
  3. Exploit maturity— → none

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

References

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

All records