dbcve.org
PythonApplication · Microsoft

CVE-2025-49714

HIGH · 7.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 2025.8.1 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Trust boundary violation in Visual Studio Code - Python extension allows an unauthorized attacker to execute code locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A trust boundary violation in the Visual Studio Code Python extension allows an unauthorized attacker to execute code locally on the affected system. The vulnerability stems from improper validation or enforcement of trust boundaries within the extension's code execution context, enabling arbitrary code to run outside intended security constraints.

MitigationUpdate the Visual Studio Code Python extension to the latest patched version provided by Microsoft. Review and restrict any extension-specific settings or workspace trust configurations that may contribute to improper trust boundary enforcement.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PythonApplication
Affected:< 2025.8.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Visual Studio Code Python extension installation
    Open VS Code and navigate to Extensions panel (Ctrl+Shift+X), or check extensions folder at %USERPROFILE%\.vscode\extensions on Windows or ~/.vscode/extensions on Linux/macOS. Look for an extension with identifier 'ms-python.python' or named 'Microsoft Python'.
    Affected if The extension is installed on the system.
  2. Retrieve installed extension version
    In VS Code Extensions panel, click on the Microsoft Python extension to view its details. The version number is displayed in the extension information panel. Alternatively, inspect the extension's package.json file in the extension folder.
    Affected if A version number is displayed in the extension details.
  3. Compare version against vulnerable range
    Compare your installed version number to the affected range: any version strictly less than 2025.8.1 is vulnerable. For example, 2025.7.0, 2025.6.0, 2025.5.0, etc. are all affected. Version 2025.8.1 and later are patched.
    Affected if Installed version is less than 2025.8.1 (e.g., 2025.7.0, 2025.6.0, etc.).

If the Microsoft Python extension is installed with a version lower than 2025.8.1, the environment is affected by this trust boundary violation vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2025.8.1 or later
Fixed in 2025.8.1
Interim mitigation

Update the Visual Studio Code Python extension to the latest patched version provided by Microsoft. Review and restrict any extension-specific settings or workspace trust configurations that may contribute to improper trust boundary enforcement.

Recommended fix High confidence

Python extension for Visual Studio Code version 2025.8.1

  1. Open Visual Studio Code
  2. Navigate to the Extensions view (Ctrl+Shift+X on Windows/Linux, Cmd+Shift+X on macOS)
  3. Search for 'Python' in the Extensions marketplace
  4. Select the Python extension by Microsoft
  5. If an update is available, click the 'Update' button to install version 2025.8.1
  6. Restart Visual Studio Code if prompted to complete the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Python Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49714 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-49714 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data