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

This month

HIGH 8.8WATCHLISTUPGRADEUPGRADEUPGRADE

CVE-2026-47295 is a high-severity flaw (CVSS 8.8) 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 over a network.

Why this priority

High severity
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.0% (top 38%)
CISA exploited list	No
Weakness	CWE-89
Published	2026-07-14
Last modified	2026-07-22

Publisher (CNA): Microsoft Corporation · Vendor: microsoft

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

Am I affected?

Timeline

2026-07-14 18:17 UTCPublished CVE record published
2026-07-22 16:50 UTCUpdated Record last modified

microsoft sql server 2016 UPGRADE

Affected: >= 13.0.6300.2 and < 13.0.6500.1 · >= 13.0.7000.253 and < 13.0.7095.1

Fixed in: 13.0.6500.1, 13.0.7095.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.6500.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.2120.1 · >= 14.0.3006.16 and < 14.0.3540.1

Fixed in: 14.0.2120.1, 14.0.3540.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.2120.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.2180.2 · >= 15.0.4003.23 and < 15.0.4480.2

Fixed in: 15.0.2180.2, 15.0.4480.2

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.2180.2 (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.1190.2 · >= 16.0.4003.1 and < 16.0.4262.2

Fixed in: 16.0.1190.2, 16.0.4262.2

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.1190.2 (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.1125.2 · >= 17.0.4006.2 and < 17.0.4060.2

Fixed in: 17.0.1125.2, 17.0.4060.2

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.1125.2 (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-47295?

sql server 2016: upgrade to 13.0.6500.1, 13.0.7095.1; sql server 2017: upgrade to 14.0.2120.1, 14.0.3540.1; sql server 2019: upgrade to 15.0.2180.2, 15.0.4480.2. Exact commands for each OS are on this page.

Is CVE-2026-47295 being exploited?

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

CVE-2026-47295 affects sql server 2016, sql server 2017, sql server 2019. Severity is high (CVSS 8.8). Improper neutralization of special elements used in an sql command ('sql injection') in SQL Server allows an authorized attacker to elevate privileges over a network.

How urgent is CVE-2026-47295?

Priority 51/100. High severity; 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-2019-1068 HIGH 8.8 EXPLOITED DOWNGRADE UPGRADE Microsoft SQL Server Remote Code Execution Vulnerability
CVE-2026-54118 CRITICAL 9.8 UPGRADE UPGRADE Deserialization of untrusted data in SQL Server allows an unauthorized attacker to execute code over a network

References

← Back to latest CVEs