CVE-2026-81383: Use of incorrectly-resolved name or reference in Visual Studio Code allows an unauthorized attacker to disclos

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

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

Q: Is CVE-2026-81383 being exploited?

CVE-2026-81383 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-81383 affect?

CVE-2026-81383 affects visual studio code. Severity is high (CVSS 7.4). Use of incorrectly-resolved name or reference in Visual Studio Code allows an unauthorized attacker to disclose information over a network.

Q: How urgent is CVE-2026-81383?

Priority 46/100. High severity; On your watchlist

This month

HIGH 7.4WATCHLISTUPGRADE

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

Use of incorrectly-resolved name or reference in Visual Studio Code allows an unauthorized attacker to disclose information over a network.

Why this priority

High severity
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	7.4 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.9% (top 40%)
CISA exploited list	No
Weakness	CWE-706
Published	2026-09-08
Last modified	2026-09-10

Publisher (CNA): Microsoft Corporation · Vendor: microsoft

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

Am I affected?

Timeline

2026-09-08 18:20 UTCPublished CVE record published
2026-09-10 14:48 UTCUpdated Record last modified

microsoft visual studio code UPGRADE

Affected: < 1.136.2

Fixed in: 1.136.2

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.136.2 (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-81383?

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

Is CVE-2026-81383 being exploited?

CVE-2026-81383 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-81383 affect?

CVE-2026-81383 affects visual studio code. Severity is high (CVSS 7.4). Use of incorrectly-resolved name or reference in Visual Studio Code allows an unauthorized attacker to disclose information over a network.

How urgent is CVE-2026-81383?

Priority 46/100. High severity; On your watchlist

Software pages

Visual Studio vulnerabilities

Related CVEs

CVE-2026-41109 HIGH 8.8 UPGRADE Improper neutralization of special elements in output used by a downstream component ('injection') in GitHub C
CVE-2026-41613 HIGH 8.8 UPGRADE Session fixation in Visual Studio Code allows an unauthorized attacker to elevate privileges over a network.
CVE-2026-41611 HIGH 7.8 UPGRADE Improper neutralization of script-related html tags in a web page (basic xss) in Visual Studio Code allows an
CVE-2026-41610 MEDIUM 6.3 UPGRADE Improper neutralization of input during web page generation ('cross-site scripting') in Visual Studio Code all
CVE-2026-57102 HIGH 8.8 UPGRADE Inclusion of functionality from untrusted control sphere in Visual Studio Code allows an unauthorized attacker

References

← Back to latest CVEs