Fetch Web Page OS protocol handler remote code execution
Impact
A remote code execution vulnerability exists in VS Code 1.132.0 and earlier versions when the Fetch Web Page tool retrieves a maliciously crafted web page. The page could cause the application's hidden web content loader to launch operating-system protocol handlers without an additional prompt through window opens or untrusted frame navigation. Extension URL overrides could also run before URI trust approval. An attacker could use these behaviors to execute code on the user's system. User interaction is required to cause the application to retrieve the malicious page.
Patches
The fix is available starting with VS Code 1.132.1. The fix (https://github.com/microsoft/vscode/pull/330308/changes/89e1c70fe1755e97a1edb4b315d60875b64311ee) mitigates this attack by denying window creation from fetched content, blocking untrusted frame and custom-protocol navigation, enforcing URL policy on web requests, and running extension URL overrides only after URI trust approval.
Workarounds
If upgrading is not immediately possible, open the chat tool picker and disable Fetch Web Page. Keep this tool disabled in every chat session until VS Code is updated.
Do not approve requests to fetch pages from untrusted sources or open untrusted vscode:// links.
Upgrade to VS Code 1.132.1 or later before re-enabling Fetch Web Page.
References
The patch for this can be...
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| vscode Product | < 1.132.1 | 1.132.1 |
Details and references
### Impact A remote code execution vulnerability exists in VS Code 1.132.0 and earlier versions when the Fetch Web Page tool retrieves a maliciously crafted web page. The page could cause the application's hidden web content loader to launch operating-system protocol handlers without an additional prompt through window opens or untrusted frame navigation. Extension URL overrides could also run before URI trust approval. An attacker could use these behaviors to execute code on the user's system. User interaction is required to cause the application to retrieve the malicious page. ### Patches The fix is available starting with VS Code 1.132.1. The fix (https://github.com/microsoft/vscode/pull/330308/changes/89e1c70fe1755e97a1edb4b315d60875b64311ee) mitigates this attack by denying window creation from fetched content, blocking untrusted frame and custom-protocol navigation, enforcing URL policy on web requests, and running extension URL overrides only after URI trust approval. ### Workarounds If upgrading is not immediately possible, open the chat tool picker and disable **Fetch Web Page**. Keep this tool disabled in every chat session until VS Code is updated. Do not approve requests to fetch pages from untrusted sources or open untrusted `vscode://` links. Upgrade to VS Code 1.132.1 or later before re-enabling **Fetch Web Page**. ### References The patch for this can be found at https://github.com/microsoft/vscode/pull/330308/changes/89e1c70fe1755e97a1edb4b315d60875b64311ee An issue for this can be found at https://github.com/microsoft/vscode/issues/330328 MSRC details for this can be found at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-59113
- CVSS 3.1
- CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-862