SQL Server Remote Code Execution Vulnerability

How could an attacker exploit this vulnerability?
An authenticated attacker with explicit permissions could exploit the vulnerability by logging in to the SQL server and could then elevate their privileges to sysadmin.

According to the CVSS metric, the attack vector is network (AV:N), and privilege required is low (PR:L). What is the target used in the context of the remote code execution?
The attacker for this vulnerability could target the server accounts in an arbitrary or remote code execution. As an authenticated user, the attacker could attempt to trigger malicious code in the context of the server's account through a network call.
The privilege requirement is low because the attacker needs to be authenticated as a normal user.

I am running SQL Server on my system. What action do I need to take?
Update your relevant version of SQL Server. Any applicable driver fixes are included in those updates.
First, determine your SQL Server version number. For more information on determining your SQL Server version number, see Microsoft Knowledge Base Article 321185 - How to determine the version, edition, and update level of SQL Server and its components., Second, in the following table, locate your version number or the version range that your version number falls within. The corresponding update is the one you need to install.
5089899: 5089899, Security update for SQL Server 2025 CU4+GDR: Security update for SQL Server 2025 CU4+GDR, 17.0.4040.1: 17.0.4040.1, 17.0.4006.2 - 17.0.4035.5: 17.0.4006.2 - 17.0.4035.5, KB5081495 - Previous SQL2025 RTM CU4: KB5081495 - Previous SQL2025 RTM CU4, 5091223: 5091223, Security update for SQL Server 2025 RTM+GDR: Security update for SQL Server 2025 RTM+GDR, 17.0.1115.1: 17.0.1115.1, 17.0.1000.7 - 17.0.1110.1: 17.0.1000.7 - 17.0.1110.1, KB5084814 - Previous SQL2025 RTM GDR: KB5084814 - Previous SQL2025 RTM GDR, 5089900: 5089900, Security update for SQL Server 2022 CU24+GDR: Security update for SQL Server 2022 CU24+GDR, 16.0.4252.3: 16.0.4252.3, 16.0.4003.1 - 16.0.4250.1: 16.0.4003.1 - 16.0.4250.1, KB5083252 - Previous SQL2022 RTM CU24: KB5083252 - Previous SQL2022 RTM CU24, 5091158: 5091158, Security update for SQL Server 2022 RTM+GDR: Security update for SQL Server 2022 RTM+GDR, 16.0.1180.1: 16.0.1180.1, 16.0.1000.6 - 16.0.1175.1: 16.0.1000.6 - 16.0.1175.1, KB5084815 - Previous SQL2022 RTM GDR: KB5084815 - Previous SQL2022 RTM GDR, 5090407: 5090407, Security update for SQL Server 2019 CU32+GDR: Security update for SQL Server 2019 CU32+GDR, 15.0.4470.1: 15.0.4470.1, 15.0.4003.23 - 15.0.4465.1: 15.0.4003.23 - 15.0.4465.1, KB 5084816 - Previous SQL2019 RTM CU32 GDR: KB 5084816 - Previous SQL2019 RTM CU32 GDR, 5090408: 5090408, Security update for SQL Server 2019 RTM+GDR: Security update for SQL Server 2019 RTM+GDR, 15.0.2170.1: 15.0.2170.1, 15.0.2000.5 - 15.0.2165.1: 15.0.2000.5 - 15.0.2165.1, KB 5084817 - Previous SQL2019 RTM GDR: KB 5084817 - Previous SQL2019 RTM GDR, 5090354: 5090354, Security update for SQL Server 2017 CU31+GDR: Security update for SQL Server 2017 CU31+GDR, 14.0.3530.2: 14.0.3530.2, 14.0.3006.16 - 14.0.3525.1: 14.0.3006.16 - 14.0.3525.1, KB 5084818 - Previous SQL2017 RTM CU31 GDR: KB 5084818 - Previous SQL2017 RTM CU31 GDR, 5090347: 5090347, Security update for SQL Server 2017 RTM+GDR: Security update for SQL Server 2017 RTM+GDR, 14.0.2110.2: 14.0.2110.2, 14.0.1000.169 - 14.0.2105.1: 14.0.1000.169 - 14.0.2105.1, KB 5084819 - Previous SQL2017 RTM GDR: KB 5084819 - Previous SQL2017 RTM GDR, 5089270: 5089270, Security update for SQL Server 2016 Azure Connect Feature Pack+GDR: Security update for SQL Server 2016 Azure Connect Feature Pack+GDR, 13.0.7085.1: 13.0.7085.1, 13.0.7000.253 - 13.0.7080.1: 13.0.7000.253 - 13.0.7080.1, KB 5084820 - Previous SQL2016 Azure Connect Feature Pack GDR: KB 5084820 - Previous SQL2016 Azure Connect Feature Pack GDR, 5089271: 5089271, Security update for SQL Server 2016 SP3+GDR: Security update for SQL Server 2016 SP3+GDR, 13.0.6490.1: 13.0.6490.1, 13.0.6300.2 - 13.0.6485.1: 13.0.6300.2 - 13.0.6485.1, KB 5084821 - Previous SQL2016 RTM GDR: KB 5084821 - Previous SQL2016 RTM GDR
The General Distribution Release (GDR) and Cumulative Update (CU) designations correspond to the two different servicing options in place for SQL Server baseline releases. A baseline can be either an RTM release or a Service Pack release.
GDR updates – cumulatively only contain security updates for the given baseline., CU updates – cumulatively contain all functional fixes and security updates for the given baseline.
For any given baseline, either the GDR or CU updates could be options (see below).
If SQL Server installation is at a baseline version, you can choose either the GDR or CU update., If SQL Server installation has intentionally only installed past GDR updates, then choose to install the GDR update package., If SQL Server installation has intentionally installed previous CU updates, then choose to install the CU security update package.
Yes. SQL Server instances on Windows Azure (IaaS) can be offered the security updates through Microsoft Update, or customers can download the security updates from Microsoft Download Center and apply them manually.

Security updates
17.0.4040.1 — https://support.microsoft.com/help/5089899
16.0.4252.3 — https://support.microsoft.com/help/5089900
14.0.2110.2 — https://support.microsoft.com/help/5090347
15.0.2170.1 — https://support.microsoft.com/help/5090408
13.0.6490.1 — https://support.microsoft.com/help/5089271
13.0.7085.1 — https://support.microsoft.com/help/5089270
14.0.3530.2 — https://support.microsoft.com/help/5090354
16.0.1180.1 — https://support.microsoft.com/help/5091158
17.0.1115.1 — https://support.microsoft.com/help/5091223
15.0.4470.1 — https://support.microsoft.com/help/5090407