LiveActive security incident?Get immediate response
CVE Record

CVE-2026-21523: GitHub Copilot and Visual Studio Code Remote Code Execution Vulnerability

Time-of-check time-of-use (toctou) race condition in GitHub Copilot and Visual Studio allows an authorized attacker to execute code over a network.

HighCVSS 8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A race condition in GitHub Copilot and Visual Studio Code can let an already authorized, low-privilege attacker execute code remotely after user interaction. Successful exploitation could compromise data, alter systems, or disrupt availability. The supplied record rates it high severity at CVSS 8.0.

Executive priority

Treat as a high-priority developer-endpoint issue. Establish exposure promptly and deploy Microsoft's official remediation. Escalate systems used for sensitive source code, credentials, production administration, or untrusted projects because successful exploitation could cause full confidentiality, integrity, and availability impact.

Technical view

CVE-2026-21523 is a CWE-367 time-of-check/time-of-use race condition. The CVSS vector indicates network reachability, low attack complexity, low privileges, required user interaction, unchanged scope, and high confidentiality, integrity, and availability impact.

Likely exposure

The supplied affected entries identify Microsoft Visual Studio Code Copilot Chat Extension 0.27.0 and Visual Studio Code 1.0.0. Exposure outside those exact entries cannot be established from the bundle. Inventory extension and editor versions, prioritizing systems that process untrusted remote content or projects.

Exploitation context

The record requires an authorized attacker and user interaction. It does not establish anonymous exploitation. KEV is false, and the supplied CVSS exploit-maturity metric is unproven. Therefore, active exploitation is not supported by the provided evidence.

Researcher notes

The bundle confirms CWE-367 and the CVSS characteristics but provides no race window, vulnerable component flow, fixed-version details, indicators of compromise, or proof of exploitation. Avoid assuming broader affected releases. Use the Microsoft advisory for current version boundaries and remediation details.

Mitigation direction

  • Review the Microsoft advisory and apply its official update or remediation guidance.
  • Prioritize affected developer workstations handling untrusted repositories, files, prompts, or remote content.
  • Restrict unnecessary access by low-privilege or external users until remediation is confirmed.
  • If immediate updating is impossible, consider disabling the affected extension after operational review.

Validation and detection

  • Inventory Visual Studio Code and Copilot Chat extension versions across managed endpoints.
  • Compare detected versions with the Microsoft advisory's current affected and fixed-version information.
  • Confirm updates are deployed and affected versions are no longer present.
  • Review endpoint telemetry for unexpected child processes or code execution associated with affected applications.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-367: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-21523 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C2.15.9microsoft

Vulnerability scoring details

Base CVSS 3.1 score

8High
CVSS 3.1 vector shape for CVE-2026-21523Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftMicrosoft Visual Studio Code CoPilot Chat Extension0.27.0Listed
MicrosoftVisual Studio Code1.0.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-367 · source CWE mapping

Time-of-check Time-of-use (TOCTOU) Race Condition

Time-of-check Time-of-use (TOCTOU) Race Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.