Skip to main content

CVE detail

CVE-2026-69306

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

CVSS 8.2 · HighBuzz score 21.9

Buzz score

Why this CVE is surfacing

Buzz score total 21.9

This all-time snapshot uses the same composite formula as Trending across a 30-year evidence window, rather than a current rolling window.

Buzz score components · mention 13.9 · diversity 8.0 · KEV 0.0 · OTX 0.0 · PoC 0.0
Mention score
13.9
3 evidence mentions in the snapshot
Diversity score
8.0
3 sources across 1 categories
KEV score
0.0
No KEV entry observed
OTX score
0.0
0 OTX pulses
PoC score
0.0
0 repos · best confidence N/A
Best PoC traction
0
Maximum stars on a matched PoC repo

Why it matters now

Mention timeline

Total mentions
3
within the 30d window
Peak daily
3
highest bucket

Evidence

Source links by recency

Newest mentions first
3 source links · newest first
  • ktop browser security patches so far this month. SharePoint: critical RCE chain by Rapid7 Today sees the publication of CVE-2026-63520 , a high-severity remote code execution in Microsoft SharePoint. Discovered by Rapid7 Senior Principal Security Researcher Stephen Fewer , and published today in coordination with Microsoft; this vulnerability is the se

    vendorwww.rapid7.comAug 11, 2026, 9:10 PM
  • The August 2026 Security Update ReviewZero Day Initiative

    g actively exploited, at least as 0-days. Again, we’ll start with the bug under active attack and move on from there. - CVE-2026-68820 - Windows Ancillary Function Driver for WinSock Elevation of Privilege Vulnerability This bug allows attackers to execute code at SYSTEM level. Bugs of this type are often paired with code execution bugs to take over a

    vendorwww.thezdi.comAug 11, 2026, 5:56 PM
  • Not failing securely ('failing open') in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.

    vendormsrc.microsoft.comAug 11, 2026, 2:00 PM

Exploit code

Public exploit repository references

Public PoC repositories are third-party, potentially unsafe artifacts. Treat their code as untrusted and use it only on authorized systems in an isolated, least-privilege environment. cvebuzz does not execute the code or verify that an exploit works.

0 repository references · best confidence N/A · max 0 stars
No public PoC repositories have been matched yet.

Related records

Similar CVEs

6 related CVEs with shared weakness or product evidence
  • CVE-2026-73421

    NextAuth.js provides authentication for Next.js. From next-auth 5.0.0-beta.0 until 5.0.0-beta.32, applications that gate access by checking only for the existence of the auth obje…

    CVSS 9.1 · Critical
    3 mentions
  • CVE-2026-70452

    rsync 3.1.0 before 3.5.0 contains an access control bypass vulnerability that allows remote attackers to circumvent hosts deny rules by inducing DNS resolution failures during hos…

    CVSS 9.1 · Critical
    3 mentions
  • CVE-2026-68746

    Not Failing Securely ('Failing Open') vulnerability in livebook-dev livebook allows an unauthenticated network client to obtain full access to a Livebook server that enforces iden…

    CVSS 7.7 · High
    6 mentions
  • CVE-2026-44094

    An unauthenticated remote attacker can enforce the system to fall back to a firmware partition with an insecure configuration including default credentials. This could allow the a…

    CVSS 8.3 · High
    1 mention
  • CVE-2026-53712

    SCRAM (Salted Challenge Response Authentication Mechanism) is part of the family of Simple Authentication and Security Layer (SASL, RFC 4422) authentication mechanisms. Prior to 3…

    CVSS 8.2 · High
    2 mentions
  • CVE-2026-62235

    Grav Flex-Objects before version 1.4.3 contains a broken access control vulnerability in the admin-next REST API that allows authenticated users with only api.access permission to…

    CVSS 2.3 · Low
    2 mentions