LiveActive security incident?Get immediate response
CVE Record

CVE-2023-36867: Visual Studio Code GitHub Pull Requests and Issues Extension Remote Code Execution Vulnerability

Visual Studio Code GitHub Pull Requests and Issues Extension Remote Code Execution Vulnerability

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This affects Visual Studio Code’s GitHub Pull Requests and Issues extension version 0.1.1. If a user interacts with malicious content or workflow, the flaw could allow code execution on the developer workstation. Impact is high because a compromised developer machine can expose source code, credentials, and build access. The bundle does not show KEV listing or active exploitation.

Executive priority

Treat as a high-priority developer workstation risk, especially in engineering environments where VS Code has access to source code, secrets, or deployment tooling.

Technical view

MSRC classifies CVE-2023-36867 as remote code execution with CVSS 3.1 score 7.8: local attack vector, low complexity, no privileges, user interaction required, unchanged scope, and high confidentiality, integrity, and availability impact. The bundle identifies only version 0.1.1 of the VS Code GitHub Pull Requests and Issues extension as affected.

Likely exposure

Exposure is most likely on developer workstations or build-adjacent systems running Visual Studio Code with the GitHub Pull Requests and Issues extension at version 0.1.1.

Exploitation context

The provided CVSS vector requires user interaction and a local attack context. The bundle marks exploit code maturity as proof-of-concept, but KEV is false and no cited source confirms active exploitation.

Researcher notes

Evidence is limited to the CVE record and MSRC advisory metadata. The title says remote code execution, while CVSS uses local attack vector and user interaction, so validation should focus on affected extension presence and user-driven exposure.

Mitigation direction

  • Check MSRC guidance for the official remediation path.
  • Update or remove affected extension version 0.1.1.
  • Prioritize developer machines with repository, credential, or build access.
  • Restrict untrusted workspace and pull request interaction until remediated.

Validation and detection

  • Inventory VS Code extensions across developer endpoints.
  • Confirm whether version 0.1.1 is installed.
  • Verify the extension is updated or removed after remediation.
  • Review endpoint telemetry for suspicious code execution from VS Code processes.
Prepared
Confidence
medium
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.

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-2023-36867 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
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/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
0Timeline events
0ADP providers
2Source links

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
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2023-36867Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftVisual Studio Code - GitHub Pull Requests and Issues Extension0.1.1Listed
Weakness

CWE details

No CWE listed

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