Skip to main content
EPSS 0.9%top 41%

CVE-2026-81381: CWE-522: Insufficiently Protected Credentials in Microsoft Visual Studio Code

0
Medium
VulnerabilityCVE-2026-81381cvecve-2026-81381cwe-522
Published: 09/08/2026 (09/08/2026, 17:14:00 UTC)
Source: CVE Database V5
Vendor/Project: Microsoft
Product: Visual Studio Code

Description

Insufficiently protected credentials in GitHub Copilot and Visual Studio Code allows an unauthorized attacker to disclose information over a network.

CVSS v3.1

Score 6.5medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C

Affected software

Microsoft

Visual Studio Code

Affected versions
>=1.0.0 <1.136.2
GitHub Actionsmore threats →ai
microsoft/vscode
pkg:github/microsoft/vscode
Affected versions
=1.0.0

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/14/2026, 22:06:41 UTC

Technical Analysis

This vulnerability, tracked as CVE-2026-81381 and categorized under CWE-522 (Insufficiently Protected Credentials), affects Microsoft Visual Studio Code and GitHub Copilot. It allows unauthorized attackers to disclose sensitive information over a network due to inadequate protection of credentials. The CVSS 3.1 base score is 6.5, indicating medium severity, with an attack vector of network, low attack complexity, no privileges required, and user interaction required. The vulnerability does not impact integrity or availability but has a high impact on confidentiality. Microsoft has published an official fix addressing this issue.

Potential Impact

An attacker can remotely disclose sensitive credential information due to insufficient protection, potentially leading to information leakage. The confidentiality impact is high, but integrity and availability are not affected. No known exploits are reported in the wild at this time.

Mitigation Recommendations

Microsoft has released an official fix for this vulnerability. Users should apply the update to Visual Studio Code version 1.136.2 or later to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
microsoft
Date Reserved
2026-08-26T18:46:26.214Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
official-fix
Vendor Advisory Urls
[{"url":"https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-81381","vendor":"Microsoft"}]

Threat ID: 6aa0456dacd9273b49faff00

Added to database: 09/08/2026, 17:27:09 UTC

Last enriched: 10/14/2026, 22:06:41 UTC

Last updated: 10/23/2026, 15:10:15 UTC

Views: 44

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses