SQL Server Management Studio 20.2: Uncontrolled Search Path Element
CVE-2025-29803 is a high-severity uncontrolled search path element vulnerability in SQL Server Management Studio 20.2 from Microsoft, with a CVSS 3.1 base score of 7.3 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, but only if a user takes part, for example by opening a link or file. The record lists version 20.2.37.0 as the first without the flaw, so updating SQL Server Management Studio 20.2 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.77% chance of exploitation within 30 days, higher than 56% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update SQL Server Management Studio 20.2 to 20.2.37.0 or a later version.
- Update Visual Studio Tools for Applications (VSTA) to 16.0.35907.0 or 17.0.35906.0, whichever matches your release line, or a later version.
- Update VSTA 2019 SDK to 16.0.35907.0 or a later version.
- Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Microsoft | SQL Server Management Studio 20.2 | 20.0 up to, but not including, 20.2.37.0 | 20.2.37.0 |
| Microsoft | Visual Studio Tools for Applications (VSTA) | 16.0 up to, but not including, 16.0.35907.0; 17.0 up to, but not including, 17.0.35906.0 | 16.0.35907.0, 17.0.35906.0 |
| Microsoft | VSTA 2019 SDK | 16.0 up to, but not including, 16.0.35907.0 | 16.0.35907.0 |
| Microsoft | VSTA 2022 SDK | 17.0 up to, but not including, 17.0.35906.0 | 17.0.35906.0 |
| Microsoft | SQL Server Management Studio | before 20.2.1 | 20.2.1 |
| Microsoft | Visual Studio Tools For Applications 2019 | before 16.0.35907.0 | 16.0.35907.0 |
| Microsoft | Visual Studio Tools For Applications 2019 SDK | before 16.0.35907.0 | 16.0.35907.0 |
| Microsoft | Visual Studio Tools For Applications 2022 | before 17.0.35906.0 | 17.0.35906.0 |
| Microsoft | Visual Studio Tools For Applications 2022 SDK | before 17.0.35906.0 | 17.0.35906.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H. Scored by CNA (microsoft.com).
Official description
Uncontrolled search path element in Visual Studio Tools for Applications and SQL Server Management Studio allows an authorized attacker to elevate privileges locally.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Uncontrolled Search Path Element
The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors.
How developers prevent this class of flaw
- Hard-code the search path to a set of known-safe values (such as system directories), or only allow them to be specified by the administrator in a configuration file. Do not allow these settings to be modified by an external party. Be careful to avoid related weaknesses such as CWE-426 and CWE-428.
- When invoking other programs, specify those programs using fully-qualified pathnames. While this is an effective approach, code that uses fully-qualified pathnames might not be portable to other systems that do not use the same pathnames. The portability can be improved by locating the full-qualified paths in a centralized, easily-modifiable location within the source code, and having the code refer to these paths.
- Remove or restrict all environment settings before invoking other programs. This includes the PATH environment variable, LD_LIBRARY_PATH, and other settings that identify the location of code libraries, and any application-specific search paths.
More Uncontrolled Search Path Element vulnerabilities (CWE-427)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Recent Uncontrolled Search Path Element vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 8.4 High severity
- 7.8 High severity
- 8.5 High severity
- 7.8 High severity
Spotted an error? Tell us.