BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-69306High confidence

Visual Studio Code Security Feature Bypass Vulnerability

Microsoft · Visual Studio Code

8.2HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-56563

No EUVD known-exploited evidence

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

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
8.2 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

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

What

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

Why

When the product encounters an error condition or failure, its design requires it to fall back to a state that is less secure than other options that are available, such as selecting the weakest encryption algorithm or using the most permissive access control restrictions.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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

Why

When the product encounters an error condition or failure, its design requires it to fall back to a state that is less secure than other options that are available, such as selecting the weakest encryption algorithm or using the most permissive access control restrictions.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Not Failing Securely ('Failing Open') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-636 ↗

CWE-636: Not Failing Securely ('Failing Open'). When the product encounters an error condition or failure, its design requires it to fall back to a state that is less secure than other options that are available, such as selecting the weakest encryption algorithm or using the most permissive access control restrictions.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N/E:U/RL:O/RC:C

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-636
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-56563Official EUVD mapping

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

Official EUVD record
BSI · German · WID-SEC-W-2026-2761Microsoft Developer Tools: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Microsoft Visual Studio Code, Microsoft Windows Server 2012, Microsoft Windows Server 2012 R2, Microsoft Windows Server 2016, Microsoft .NET Framework, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows Server 2025, Microsoft PowerShell, Microsoft Windows, Microsoft .NET, Microsoft Visual Studio 2022 und Microsoft Visual Studio 2026 ausnutzen, um beliebigen Programmcode auszuführen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, und um Sicherheitsvorkehrungen zu umgehen.

Official advisory
CERT-FR · French · CERTFR-2026-AVI-1004Multiples vulnérabilités dans les produits Microsoft

ulletin de sécurité Microsoft CVE-2026-65768 du 11 août 2026 Bulletin de sécurité Microsoft CVE-2026-65769 du 11 août 2026 Bulletin de sécurité Microsoft CVE-2026-65811 du 11 août 2026 Bulletin de sécurité Microsoft CVE-2026-65813 du 11 août 2026 Bulletin de sécurité Microsoft CVE-2026-65815 du 11 août 2026 Bulletin de sécurité Microsoft CVE-2026-66301 du 11 août 2026 Bulletin de sécurité Microsoft CVE-2026-66805 du 11 août 2026 Bulletin de sécurité Microsoft CVE-2026-66808 du 11 août 2026 Bulletin de sécurité Microsoft CVE-2026-68821 du 11 août 2026 Bulletin de sécurité Microsoft CVE-2026-69278 du 11 août 2026 Bulletin de sécurité Microsoft CVE-2026-69306 du 11 août 2026 Bulletin de sécurité Microsoft CVE-2026-69320 du 11 août 2026 Bulletin de sécurité Microsoft CVE-2026-70306 du 11 août 2026 Bulletin de sécurité Microsoft CVE-2026-70321 du 11 août 2026 Bulletin de sécurité Microsoft CVE-2026-70324 du 11 août 2026 Bulletin de sécurité Microsoft CVE-2026-70326 du 11 août 2026 Bulletin de sécurité Microsoft CVE-2026-70335 du 11 août 2026 Bulletin de sécurité Microsoft CVE-2026-70336 du 11 août 2026 Bulletin de sécurité Microsoft CVE-2026-70337 du 11 août 2026 Bulletin de sécurité Microsoft CVE-2026-70338 du 11 août 2026 Bulletin de sécurité Microsoft CVE-2026-70354 du 11 août 2026 Bulletin de s

Official advisory
CSIRT Italia · Italian · aggiornamenti-mensili-microsoft-23Aggiornamenti Mensili Microsoft

nuova finestra - - CVE-2026-70318 : apre una nuova finestra - - CVE-2026-70317 : apre una nuova finestra - - CVE-2026-70316 : apre una nuova finestra - - CVE-2026-70315 : apre una nuova finestra - - CVE-2026-70314 : apre una nuova finestra - - CVE-2026-70313 : apre una nuova finestra - - CVE-2026-70312 : apre una nuova finestra - - CVE-2026-70311 : apre una nuova finestra - - CVE-2026-70310 : apre una nuova finestra - - CVE-2026-70307 : apre una nuova finestra - - CVE-2026-70306 : apre una nuova finestra - - CVE-2026-70304 : apre una nuova finestra - - CVE-2026-70130 : apre una nuova finestra - - CVE-2026-69320 : apre una nuova finestra - - CVE-2026-69306 : apre una nuova finestra - - CVE-2026-69278 : apre una nuova finestra - - CVE-2026-68823 : apre una nuova finestra - - CVE-2026-68821 : apre una nuova finestra - - CVE-2026-68820 : apre una nuova finestra - Presente CVE-2026-68819 : apre una nuova finestra - - CVE-2026-68817 : apre una nuova finestra - - CVE-2026-68816 : apre una nuova finestra - - CVE-2026-68815 : apre una nuova finestra - - CVE-2026-68814 : apre una nuova finestra - - CVE-2026-68813 : apre una nuova finestra - - CVE-2026-68812 : apre una nuova finestra - - CVE-2026-68811 : apre una nuova finestra - - CVE-2026-68810 : apre una nuova finestra - - CVE-2026-68809 : apre una n

Official advisory
NCSC-NL · Dutch · NCSC-2026-0285Kwetsbaarheden verholpen in Microsoft Developer Tools

A failing open security flaw in Visual Studio Code enables unauthorized attackers to bypass security features remotely over a network.

Official advisory
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
1.0.0 < 1.135
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 11 Aug 2026 · Last source change 8 Sept 2026, 21:53 UTC · CWE-636 · Not Failing Securely ('Failing Open')

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-56563
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceOther authority
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    1.0.0 < 2026.3.1 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    1.0.0 < 1.135 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    1.0.0 < 1.132.1 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    1.0.0 < 2026.3.1 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-56563↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-69306 · cve.blacktree.nl