CVE-2026-47282: Insufficiently protected credentials in GitHub Copilot and Visual Studio Code allows an unauthorized attacker

Q: How do I fix CVE-2026-47282?

visual studio code: upgrade to 1.128.1. Exact commands for each OS are on this page.

Q: Is CVE-2026-47282 being exploited?

CVE-2026-47282 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-47282 affect?

CVE-2026-47282 affects visual studio code. Severity is medium (CVSS 6.5). Insufficiently protected credentials in GitHub Copilot and Visual Studio Code allows an unauthorized attacker to disclose information over a network.

Q: How urgent is CVE-2026-47282?

Priority 42/100. On your watchlist

This month

MEDIUM 6.5WATCHLISTUPGRADE

CVE-2026-47282 is a medium-severity flaw (CVSS 6.5) affecting visual studio code. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.9% (top 41%)
CISA exploited list	No
Weakness	CWE-200, CWE-522
Published	2026-07-14
Last modified	2026-10-24

Publisher (CNA): Microsoft Corporation · Vendor: microsoft

Last updated 2026-10-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-07-14 17:16 UTCPublished CVE record published
2026-10-24 21:10 UTCUpdated Record last modified

microsoft visual studio code UPGRADE

Affected: < 1.128.1

Fixed in: 1.128.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy visual-studio-code || rpm -q visual-studio-code || visual-studio-code --version

2. UPGRADE to 1.128.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade visual-studio-code

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade visual-studio-code

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-47282?

visual studio code: upgrade to 1.128.1. Exact commands for each OS are on this page.

Is CVE-2026-47282 being exploited?

CVE-2026-47282 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-47282 affect?

CVE-2026-47282 affects visual studio code. Severity is medium (CVSS 6.5). Insufficiently protected credentials in GitHub Copilot and Visual Studio Code allows an unauthorized attacker to disclose information over a network.

How urgent is CVE-2026-47282?

Priority 42/100. On your watchlist

Software pages

GitHub vulnerabilities · Visual Studio vulnerabilities

Related CVEs

CVE-2026-57102 HIGH 8.8 UPGRADE Inclusion of functionality from untrusted control sphere in Visual Studio Code allows an unauthorized attacker
CVE-2026-50520 HIGH 8.4 UPGRADE Improper neutralization of special elements used in a command ('command injection') in Visual Studio Code allo
CVE-2026-57101 HIGH 7.1 UPGRADE Improper neutralization of input during web page generation ('cross-site scripting') in Visual Studio Code all
CVE-2026-45496 MEDIUM 5.5 UPGRADE Improper limitation of a pathname to a restricted directory ('path traversal') in Visual Studio Code allows an
CVE-2026-69320 HIGH 8.8 UPGRADE Improper neutralization of special elements used in an os command ('os command injection') in Visual Studio Co

References

← Back to latest CVEs