Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-77487: Improper access control in SQL Server allows an authorized attacker to elevate privileges over a network.

50
This month
HIGH 8.8WATCHLISTUPGRADEUPGRADEUPGRADE

CVE-2026-77487 is a high-severity flaw (CVSS 8.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.

Improper access control 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 score8.8 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.8% (top 44%)
CISA exploited listNo
WeaknessCWE-284
Published2026-09-08
Last modified2026-09-15
Publisher (CNA): Microsoft Corporation · Vendor: microsoft

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

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.
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-77487?

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-77487 being exploited?

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

CVE-2026-77487 affects sql server 2017, sql server 2019, sql server 2022. Severity is high (CVSS 8.8). Improper access control in SQL Server allows an authorized attacker to elevate privileges over a network.

How urgent is CVE-2026-77487?

Priority 50/100. High severity; 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.