# CVE-2026-67631 — Microsoft SQL Server 2017 (CU 31)

> As of 2026-10-08, CVE-2026-67631 is a CRITICAL-severity vulnerability in Microsoft SQL Server 2017 (CU 31), CVSS v3.1 9.8, EPSS 0.9% (60.9th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-67631, most recently “Microsoft September 2026 Patch Tuesday — 999 CVEs, 3 actively exploited zero-days (CVE-2026-85880, CVE-2026-81963, CVE-2026-85046)”.

**Last updated:** 2026-10-08

## What is CVE-2026-67631?

Heap-based buffer overflow in SQL Server allows an unauthorized attacker to execute code over a network.

The record classifies CVE-2026-67631 under weakness class [CWE-122](https://intel.threadlinqs.com/cwe/CWE-122). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 8 affected-product entries are recorded, across 1 vendor, listed below. The identifier was first published 72 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 9.8 — CRITICAL (`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`)
- **EPSS (FIRST):** 0.9% probability of exploitation in the next 30 days, higher than 60.9% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 7.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-09-08

## Is CVE-2026-67631 being exploited?

It currently carries a trending score of 42 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [Microsoft](https://intel.threadlinqs.com/vendors/microsoft): SQL Server 2017 (CU 31), SQL Server 2017 (GDR), SQL Server 2019 (CU 32), SQL Server 2019 (GDR), SQL Server 2022 (CU 26), SQL Server 2022 (GDR), SQL Server 2025 (CU8), SQL Server 2025 for x64-based Systems (GDR)

## How to fix CVE-2026-67631

The record marks a vendor fix as available for CVE-2026-67631. Patch reference: [https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-67631](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-67631). Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

## Threat activity tracking CVE-2026-67631

1 tracked threat in the Threadlinqs corpus references CVE-2026-67631, either in the campaign’s CVE list or as an indicator on the campaign record.

- [Microsoft September 2026 Patch Tuesday — 999 CVEs, 3 actively exploited zero-days (CVE-2026-85880, CVE-2026-81963, CVE-2026-85046)](https://intel.threadlinqs.com/threat/TL-2026-2407) — CRITICAL · 2026-09-08

## Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [msrc.microsoft.com — vendor advisory](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-67631)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-67631
Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Sign up free (Blue): https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
