Should you update to Visual Studio Code 1.141.1?
Yes, soon. Visual Studio Code 1.141.1 is a security update Microsoft released on 13 Oct 2026 for Mac, Windows and Linux. It fixes 10 security flaws, 0 rated critical and 10 important by Microsoft.[1] None of them is known to be used in attacks.
It is the newest Visual Studio Code release, so it’s the one to have.
Should you update?
Yes, soon. None of its fixes is known to be used in attacks yet. Automatic updates will install it for you. Every security update closes holes that become public the moment it ships, so the risk of staying on the old version only grows. Waiting a week to see if others hit problems is a common habit; with a security update it’s the wrong trade.
Is Visual Studio Code 1.141.1 safe to install?
Yes. It’s Microsoft’s own security release, and updates rarely go wrong; a backup makes it painless if one does. The one unsafe way to get it is from a link: Microsoft never sends updates by email, text or pop-up, so install it only from VS Code’s own Check for Updates.
What it fixes
Microsoft lists 10 security flaws, 0 rated critical and 10 important by Microsoft.[1] The 10 critical and important ones are:
| Flaw | Severity | What Microsoft calls it |
|---|---|---|
CVE-2026-69370 | Important | Visual Studio Code Remote Code Execution Vulnerability |
CVE-2026-70098 | Important | Visual Studio Code Remote Code Execution Vulnerability |
CVE-2026-102229 | Important | Visual Studio Code Information Disclosure Vulnerability |
CVE-2026-102231 | Important | Visual Studio Code Security Feature Bypass Vulnerability |
CVE-2026-102232 | Important | Visual Studio Code Security Feature Bypass Vulnerability |
CVE-2026-102233 | Important | Visual Studio Code Security Feature Bypass Vulnerability |
CVE-2026-102234 | Important | Visual Studio Code Security Feature Bypass Vulnerability |
CVE-2026-102235 | Important | Visual Studio Code Remote Code Execution Vulnerability |
CVE-2026-102238 | Important | Visual Studio Code Remote Code Execution Vulnerability |
CVE-2026-102851 | Important | Visual Studio Code Security Feature Bypass Vulnerability |
How to update, and how long it takes
A minute. VS Code restarts.
- Open VS Code and click the gear at the bottom left.Choose Check for Updates… (on a Mac it’s also under Code in the menu bar).
- Click Restart to Update when it appears.Your open files and windows come back after the restart.
To check it worked: Help → About (Code → About Visual Studio Code on a Mac): the version is on the first line, e.g. 1.141.1. It should say 1.141.1 or later.
1.136.2 vs 1.141.1
Visual Studio Code 1.136.2, released 8 Sep 2026, fixed 12 security flaws. Visual Studio Code 1.141.1 fixes 10 security flaws and includes the fixes before it, so going straight to 1.141.1 gets you both.
- Before: Visual Studio Code 1.136.2, 8 Sep 2026, 12 security flaws
- After: none yet. This is the newest.
- Visual Studio Code updates, every release and the latest version
- Updates, the latest version of everything HARD tracks
References
- ^ Microsoft. “Microsoft Security Update Guide, Visual Studio Code 1.141.1”, 13 Oct 2026.