Secuno
ENNL
Book demo

CVE-2026-81379

Microsoft Visual Studio Code vulnerability

8.2 HIGHEPSS 0.54%
  1. Published8 Sept 2026

Description

Not failing securely ('failing open') in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionRequired
ScopeChanged
ConfidentialityHigh
IntegrityLow
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N

Affected products

Microsoft Visual Studio Code< 1.136.2

Remediation

Fixed in
Microsoft Visual Studio Code≥ 1.136.2

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-958489.1
Moquette is a lightweight Java MQTT broker. Prior to 0.18.1, when a configured…
CVE-2026-775608.1
Tinyauth is an authentication and authorization server. Prior to 5.1.2, Tinyauth…
CVE-2026-183298.2
Description NGINX JavaScript (njs) and QuickJS (qjs) engines have a vulnerability when…
CVE-2026-693068.2
Not failing securely ('failing open') in Visual Studio Code allows an unauthorized…
CVE-2026-687468.8
Not Failing Securely ('Failing Open') vulnerability in livebook-dev livebook allows an…
CVE-2026-440948.6
An unauthenticated remote attacker can enforce the system to fall back to a firmware…

Frequently asked

Is CVE-2026-81379 being actively exploited?

CVE-2026-81379 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.54%.

How severe is CVE-2026-81379?

CVE-2026-81379 has a CVSS 3.1 base score of 8.2, rated high. EPSS estimates a 0.54% probability of exploitation.

Which products are affected by CVE-2026-81379?

Affected products include Microsoft Visual Studio Code.

How do I fix CVE-2026-81379?

Upgrade affected software to a fixed version, for example Microsoft Visual Studio Code 1.136.2 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-81379 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.