Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.new Create a CVE report
Check your stack
CVE-2026-69306high8.2

Visual Studio Code Security Feature Bypass Vulnerability

Impact

Visual Studio Code versions 1.0.0 to 1.132.1 have a security feature bypass vulnerability due to not failing securely, allowing an unauthorized attacker to bypass a security feature over a network. The weakness is described as 'Not Failing Securely' ('Failing Open').

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

Microsoft · microsoft

Visual Studio Code

1 range
microsoft version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

1.0.0 → before 1.132.1

custom versions

unaffected

unknown

Other versions: unknown

Original source description

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

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-69306

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-636 ↗

CWE-636: Not Failing Securely ('Failing Open')

microsoft

Related →

Environment requirements

These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.

microsoft · platform conditions

Any condition may hold

Vulnerable product

cpe:2.3:a:microsoft:visual_studio_code:*:*:*:*:*:*:*:*

From (inclusive): 1.0.0

Before: 1.132.1

Original applicability statements
[
  {
    "nodes": [
      {
        "operator": "OR",
        "negate": false,
        "cpeMatch": [
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:a:microsoft:visual_studio_code:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "1.0.0",
            "versionEndExcluding": "1.132.1"
          }
        ]
      }
    ]
  }
]
Contributing organizations · 2
microsoft

Assigning organization

2026-10-30
CISA-ADP

Additional data publisher

2026-08-11

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

1 sources
msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69306
vendor-advisorymicrosoft