Local security feature bypass
Published Aug 11, 2026 · Updated Aug 25, 2026
Incorrect authorization in Visual Studio Code before 1.132.1 allows attackers to bypass a security feature locally. Microsoft has not disclosed the affected component or check; the public record states only that an authorization decision in Visual Studio Code can be defeated. Microsoft's CVSS vector requires local access and user interaction, so exposure is limited to systems where an attacker can drive local VS Code actions in the current user context.
Summary
What happened
Incorrect authorization in Visual Studio Code before 1.132.1 allows attackers to bypass a security feature locally. Microsoft has not disclosed the affected component or check; the public record states only that an authorization decision in Visual Studio Code can be defeated. Microsoft's CVSS vector requires local access and user interaction, so exposure is limited to systems where an attacker can drive local VS Code actions in the current user context.
The record
- CVE
- CVE-2026-69278
- Published
- Aug 11, 2026
- Updated
- Aug 25, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, CWE-693
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo