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

> Attackers can execute arbitrary code via the GitHub Pull Requests and Issues extension in Visual Studio Code.

- **Severity:** High 7.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Jul 2023
- **Updated:** 1 Jan 2025
- **Also known as:** GHSA-wqgm-j3cr-757w

## What is CVE-2023-36867?

CVE-2023-36867 is a high-severity code injection vulnerability in Microsoft Visual Studio Code - GitHub Pull Requests and Issues Extension, published on 11 Jul 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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

## Which versions are affected by CVE-2023-36867?

It affects 1 product.


Products: Github Pull Requests and Issues.

## How do I fix CVE-2023-36867?

No fix has been published for CVE-2023-36867 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-36867 being exploited?

There is no known exploitation of CVE-2023-36867 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-36867 and fix it if it is affected.

What it is: CVE-2023-36867 is a high-severity code injection vulnerability in Microsoft Visual Studio Code - GitHub Pull Requests and Issues Extension, published on 11 Jul 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-36867 in the wild and no public exploit code.

Affected product: Microsoft Visual Studio Code - GitHub Pull Requests and Issues Extension. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-36867/ (Markdown: https://insights.sbomify.com/CVE-2023-36867/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-36867
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-36867
- OSV: https://osv.dev/vulnerability/CVE-2023-36867

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-36867/
Summaries are generated and may contain mistakes; the official description above is the record.