Microsoft Visual Studio Code up to 1.132.0 improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Microsoft Visual Studio Code up to 1.132.0. Affected by this vulnerability is an unknown functionality. This manipulation causes improper authorization. This vulnerability is handled as CVE-2026-69306. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in Microsoft Visual Studio Code up to 1.132.0. It has been declared as critical. Affected by this vulnerability is an unknown code. The manipulation with an unknown input leads to a improper authorization vulnerability. The CWE definition for the vulnerability is CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Not failing securely ('failing open') in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.
The advisory is shared at msrc.microsoft.com. This vulnerability is known as CVE-2026-69306 since 08/03/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/20/2026). MITRE ATT&CK project uses the attack technique T1548.002 for this issue.
Upgrading to version 1.132.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-2761). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Microsoft PowerShell
- Red Hat Enterprise Linux
- Fedora Linux
- Microsoft Windows Server 2016
- Microsoft Windows Server 2019
- Microsoft Windows Server 2022
- Microsoft .NET Framework
- Microsoft Visual Studio Code
- Microsoft Windows Server 2012
- Microsoft Windows Server 2012 R2
- Microsoft Windows Server 2025
- RESF Rocky Linux
- Microsoft Windows
- Microsoft .NET
- Ubuntu Linux
- Oracle Linux
- Microsoft Visual Studio 2022
- Microsoft Visual Studio 2026
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper authorizationCWE: CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Visual Studio Code 1.132.1
Timeline
08/03/2026 CVE reserved08/11/2026 VulDB entry created
08/12/2026 Advisory disclosed
08/20/2026 VulDB entry last update
Sources
Vendor: microsoft.comAdvisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2026-69306 (🔒)
GCVE (CVE): GCVE-0-2026-69306
GCVE (VulDB): GCVE-100-388861
CERT Bund: WID-SEC-2026-2761 - Microsoft Developer Tools: Mehrere Schwachstellen
Entry
Created: 08/12/2026 00:58Updated: 08/20/2026 05:58
Changes: 08/12/2026 00:58 (54), 08/15/2026 03:22 (7), 08/20/2026 05:58 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.