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

This week

CRITICAL 9.8REMOTEWATCHLISTUPGRADEUPGRADEUPGRADE

CVE-2026-67631 is a critical-severity flaw (CVSS 9.8) affecting sql server 2017, sql server 2019, sql server 2022. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

Critical severity
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.0% (top 38%)
CISA exploited list	No
Weakness	CWE-122
Published	2026-09-08
Last modified	2026-09-17

Publisher (CNA): Microsoft Corporation · Vendor: microsoft

Last updated 2026-09-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-09-08 18:18 UTCPublished CVE record published
2026-09-17 20:17 UTCUpdated Record last modified

microsoft sql server 2017 UPGRADE

Affected: < 14.0.2130.4 · >= 14.0.3006.16 and < 14.0.3550.4

Fixed in: 14.0.2130.4, 14.0.3550.4

Safe to downgrade to: a release before 14.0.3006.16

1. Check installed version

apt-cache policy sql-server-2017 || rpm -q sql-server-2017 || sql-server-2017 --version

2. UPGRADE to 14.0.2130.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade sql-server-2017

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade sql-server-2017

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 14.0.3006.16 (Debian / Ubuntu)

apt-cache madison sql-server-2017 sudo apt install sql-server-2017=<VERSION_BEFORE_14.0.3006.16> sudo apt-mark hold sql-server-2017

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list sql-server-2017 sudo dnf downgrade sql-server-2017-<VERSION_BEFORE_14.0.3006.16> sudo dnf versionlock add sql-server-2017

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

microsoft sql server 2019 UPGRADE

Affected: < 15.0.2190.7 · >= 15.0.4003.23 and < 15.0.4490.9

Fixed in: 15.0.2190.7, 15.0.4490.9

Safe to downgrade to: a release before 15.0.4003.23

1. Check installed version

apt-cache policy sql-server-2019 || rpm -q sql-server-2019 || sql-server-2019 --version

2. UPGRADE to 15.0.2190.7 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade sql-server-2019

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade sql-server-2019

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 15.0.4003.23 (Debian / Ubuntu)

apt-cache madison sql-server-2019 sudo apt install sql-server-2019=<VERSION_BEFORE_15.0.4003.23> sudo apt-mark hold sql-server-2019

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list sql-server-2019 sudo dnf downgrade sql-server-2019-<VERSION_BEFORE_15.0.4003.23> sudo dnf versionlock add sql-server-2019

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

microsoft sql server 2022 UPGRADE

Affected: < 16.0.1200.5 · >= 16.0.4003.1 and < 16.0.4275.2

Fixed in: 16.0.1200.5, 16.0.4275.2

Safe to downgrade to: a release before 16.0.4003.1

1. Check installed version

apt-cache policy sql-server-2022 || rpm -q sql-server-2022 || sql-server-2022 --version

2. UPGRADE to 16.0.1200.5 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade sql-server-2022

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade sql-server-2022

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 16.0.4003.1 (Debian / Ubuntu)

apt-cache madison sql-server-2022 sudo apt install sql-server-2022=<VERSION_BEFORE_16.0.4003.1> sudo apt-mark hold sql-server-2022

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list sql-server-2022 sudo dnf downgrade sql-server-2022-<VERSION_BEFORE_16.0.4003.1> sudo dnf versionlock add sql-server-2022

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

microsoft sql server 2025 UPGRADE

Affected: < 17.0.1135.8 · >= 17.0.4006.2 and < 17.0.4085.5

Fixed in: 17.0.1135.8, 17.0.4085.5

Safe to downgrade to: a release before 17.0.4006.2

1. Check installed version

apt-cache policy sql-server-2025 || rpm -q sql-server-2025 || sql-server-2025 --version

2. UPGRADE to 17.0.1135.8 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade sql-server-2025

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade sql-server-2025

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 17.0.4006.2 (Debian / Ubuntu)

apt-cache madison sql-server-2025 sudo apt install sql-server-2025=<VERSION_BEFORE_17.0.4006.2> sudo apt-mark hold sql-server-2025

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list sql-server-2025 sudo dnf downgrade sql-server-2025-<VERSION_BEFORE_17.0.4006.2> sudo dnf versionlock add sql-server-2025

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

Fedora ELN · xfsdump · FIXED · 3.3.0-3.eln159 · FEDORA-2026-6e9bb3f901 · source

sudo dnf upgrade --advisory=FEDORA-2026-6e9bb3f901

Fedora 46 · fio · FIXED · 3.43-2.fc46 · FEDORA-2026-b36219886b · source

sudo dnf upgrade --advisory=FEDORA-2026-b36219886b

Microsoft SQL Server 2025 for x64-based Systems (CU8) · KB5122769 · FIXED · 17.0.4085.5 · KB5122769 · source

Install KB5122769 via Windows Update, then verify: Get-HotFix -Id KB5122769

Microsoft SQL Server 2022 for x64-based Systems (CU 26) · KB5122768 · FIXED · 16.0.4275.2 · KB5122768 · source

Install KB5122768 via Windows Update, then verify: Get-HotFix -Id KB5122768

Microsoft SQL Server 2017 for x64-based Systems (GDR) · KB5122775 · FIXED · 14.0.2130.4 · KB5122775 · source

Install KB5122775 via Windows Update, then verify: Get-HotFix -Id KB5122775

Microsoft SQL Server 2019 for x64-based Systems (GDR) · KB5122773 · FIXED · 15.0.2190.7 · KB5122773 · source

Install KB5122773 via Windows Update, then verify: Get-HotFix -Id KB5122773

Microsoft SQL Server 2017 for x64-based Systems (CU 31) · KB5122774 · FIXED · 14.0.3550.4 · KB5122774 · source

Install KB5122774 via Windows Update, then verify: Get-HotFix -Id KB5122774

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-67631?

sql server 2017: upgrade to 14.0.2130.4, 14.0.3550.4; sql server 2019: upgrade to 15.0.2190.7, 15.0.4490.9; sql server 2022: upgrade to 16.0.1200.5, 16.0.4275.2. Exact commands for each OS are on this page.

Is CVE-2026-67631 being exploited?

CVE-2026-67631 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-67631 affect?

CVE-2026-67631 affects sql server 2017, sql server 2019, sql server 2022. Severity is critical (CVSS 9.8). Heap-based buffer overflow in SQL Server allows an unauthorized attacker to execute code over a network.

How urgent is CVE-2026-67631?

Priority 60/100. Critical severity; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Microsoft SQL Server vulnerabilities

Related CVEs

CVE-2026-32176 MEDIUM 6.7 UPGRADE UPGRADE Improper neutralization of special elements used in an sql command ('sql injection') in SQL Server allows an a
CVE-2026-40370 HIGH 8.8 UPGRADE UPGRADE External control of file name or path in SQL Server allows an authorized attacker to execute code over a netwo
CVE-2026-32167 MEDIUM 6.7 UPGRADE UPGRADE Improper neutralization of special elements used in an sql command ('sql injection') in SQL Server allows an a
CVE-2026-69562 MEDIUM 6.5 UPGRADE UPGRADE Out-of-bounds read in SQL Server allows an unauthorized attacker to disclose information over a network.
CVE-2026-67630 MEDIUM 6.5 UPGRADE UPGRADE Out-of-bounds read in SQL Server allows an authorized attacker to disclose information over a network.

References

← Back to latest CVEs