Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-32167: Improper neutralization of special elements used in an sql command ('sql injection') in SQL Server allows an a

34
Routine
MEDIUM 6.7WATCHLISTUPGRADEUPGRADEUPGRADE

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

Improper neutralization of special elements used in an sql command ('sql injection') in SQL Server allows an authorized attacker to elevate privileges locally.

Why this priority

  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score6.7 (Medium)
Attack vectorLocal
Attack complexityLow
Privileges neededHigh
User interactionNone
EPSS exploit chance0.3% (top 78%)
CISA exploited listNo
WeaknessCWE-89
Published2026-04-14
Last modified2026-10-26
Publisher (CNA): Microsoft Corporation · Vendor: microsoft

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

microsoft sql server 2016 UPGRADE
Affected: >= 13.0.6300.2 and < 13.0.6485.1 · >= 13.0.7000.253 and < 13.0.7080.1
Fixed in: 13.0.6485.1, 13.0.7080.1
Safe to downgrade to: a release before 13.0.6300.2
1. Check installed version
apt-cache policy sql-server-2016 || rpm -q sql-server-2016 || sql-server-2016 --version
2. UPGRADE to 13.0.6485.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade sql-server-2016
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade sql-server-2016
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 13.0.6300.2 (Debian / Ubuntu)
apt-cache madison sql-server-2016 sudo apt install sql-server-2016=<VERSION_BEFORE_13.0.6300.2> sudo apt-mark hold sql-server-2016
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list sql-server-2016 sudo dnf downgrade sql-server-2016-<VERSION_BEFORE_13.0.6300.2> sudo dnf versionlock add sql-server-2016
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 2017 UPGRADE
Affected: >= 14.0.1000.169 and < 14.0.2105.1 · >= 14.0.3006.16 and < 14.0.3525.1
Fixed in: 14.0.2105.1, 14.0.3525.1
Safe to downgrade to: a release before 14.0.1000.169
1. Check installed version
apt-cache policy sql-server-2017 || rpm -q sql-server-2017 || sql-server-2017 --version
2. UPGRADE to 14.0.2105.1 (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.1000.169 (Debian / Ubuntu)
apt-cache madison sql-server-2017 sudo apt install sql-server-2017=<VERSION_BEFORE_14.0.1000.169> 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.1000.169> 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.2000.5 and < 15.0.2165.1 · >= 15.0.4003.23 and < 15.0.4465.1
Fixed in: 15.0.2165.1, 15.0.4465.1
Safe to downgrade to: a release before 15.0.2000.5
1. Check installed version
apt-cache policy sql-server-2019 || rpm -q sql-server-2019 || sql-server-2019 --version
2. UPGRADE to 15.0.2165.1 (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.2000.5 (Debian / Ubuntu)
apt-cache madison sql-server-2019 sudo apt install sql-server-2019=<VERSION_BEFORE_15.0.2000.5> 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.2000.5> 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.1000.6 and < 16.0.1175.1 · >= 16.0.4003.1 and < 16.0.4250.1
Fixed in: 16.0.1175.1, 16.0.4250.1
Safe to downgrade to: a release before 16.0.1000.6
1. Check installed version
apt-cache policy sql-server-2022 || rpm -q sql-server-2022 || sql-server-2022 --version
2. UPGRADE to 16.0.1175.1 (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.1000.6 (Debian / Ubuntu)
apt-cache madison sql-server-2022 sudo apt install sql-server-2022=<VERSION_BEFORE_16.0.1000.6> 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.1000.6> 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.1000.7 and < 17.0.1110.1 · >= 17.0.4006.2 and < 17.0.4030.1
Fixed in: 17.0.1110.1, 17.0.4030.1
Safe to downgrade to: a release before 17.0.1000.7
1. Check installed version
apt-cache policy sql-server-2025 || rpm -q sql-server-2025 || sql-server-2025 --version
2. UPGRADE to 17.0.1110.1 (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.1000.7 (Debian / Ubuntu)
apt-cache madison sql-server-2025 sudo apt install sql-server-2025=<VERSION_BEFORE_17.0.1000.7> 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.1000.7> 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.
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-32167?

sql server 2016: upgrade to 13.0.6485.1, 13.0.7080.1; sql server 2017: upgrade to 14.0.2105.1, 14.0.3525.1; sql server 2019: upgrade to 15.0.2165.1, 15.0.4465.1. Exact commands for each OS are on this page.

Is CVE-2026-32167 being exploited?

CVE-2026-32167 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-32167 affect?

CVE-2026-32167 affects sql server 2016, sql server 2017, sql server 2019. Severity is medium (CVSS 6.7). Improper neutralization of special elements used in an sql command ('sql injection') in SQL Server allows an authorized attacker to elevate privileges locally.

How urgent is CVE-2026-32167?

Priority 34/100. On your watchlist

Software pages

Microsoft SQL Server vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.