CVE-2026-32167 [Medium] | SQL Injection in Sql Server 2016

CVE-2026-32167 is rated Low Risk (32.6/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.05%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-04-15	—	0.05%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-04-15

—

0.05%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
6.7	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	0.8	5.9	[email protected]
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

6.7

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

0.8

5.9

[email protected]

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

[email protected]

Affected software / configurations for CVE-2026-32167

Vendor	Product	Version	Raw CPE
microsoft	sql_server_2016	>= 13.0.6300.2, < 13.0.6485.1	cpe:2.3:a:microsoft:sql_server_2016:::::::x64:*
microsoft	sql_server_2016	>= 13.0.7000.253, < 13.0.7080.1	cpe:2.3:a:microsoft:sql_server_2016:::::::x64:*
microsoft	sql_server_2017	>= 14.0.1000.169, < 14.0.2105.1	cpe:2.3:a:microsoft:sql_server_2017:::::::x64:*
microsoft	sql_server_2017	>= 14.0.3006.16, < 14.0.3525.1	cpe:2.3:a:microsoft:sql_server_2017:::::::x64:*
microsoft	sql_server_2019	>= 15.0.2000.5, < 15.0.2165.1	cpe:2.3:a:microsoft:sql_server_2019:::::::x64:*
microsoft	sql_server_2019	>= 15.0.4003.23, < 15.0.4465.1	cpe:2.3:a:microsoft:sql_server_2019:::::::x64:*
microsoft	sql_server_2022	>= 16.0.1000.6, < 16.0.1175.1	cpe:2.3:a:microsoft:sql_server_2022:::::::x64:*
microsoft	sql_server_2022	>= 16.0.4003.1, < 16.0.4250.1	cpe:2.3:a:microsoft:sql_server_2022:::::::x64:*
microsoft	sql_server_2025	>= 17.0.1000.7, < 17.0.1110.1	cpe:2.3:a:microsoft:sql_server_2025:::::::x64:*
microsoft	sql_server_2025	>= 17.0.4006.2, < 17.0.4030.1	cpe:2.3:a:microsoft:sql_server_2025:::::::x64:*

References for CVE-2026-32167

URL	Tags
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-32167	Vendor Advisory

URL

CVE-2026-32167 | SQL Server Elevation of Privilege Vulnerability

Exploit prediction scoring system (EPSS) score for CVE-2026-32167

Common vulnerability scoring system (CVSS) metrics for CVE-2026-32167

Weakness enumeration for CVE-2026-32167

Affected software / configurations for CVE-2026-32167

References for CVE-2026-32167