Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.64% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-65675High confidence
CoPilot Chat Security Feature Bypass Vulnerability
Microsoft · Microsoft Visual Studio Code CoPilot Chat Extension
7.1HighCVSS 3.1
Within 7 days
Patch availableHigh technical severity; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Microsoft Microsoft Visual Studio Code CoPilot Chat Extension and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
msrc_CVE-2026-65675 · CSAF 2.0 · revision 4 · finalMicrosoft Security Response CenterCoPilot Chat Security Feature Bypass Vulnerability
The vendor explicitly identifies these products as affected by this CVE.
- Microsoft Visual Studio Code CoPilot Chat Extension <1.132.1
- Summary
- Microsoft
- Remediation
- 1.132.1:Security Update:https://code.visualstudio.com/updates/v1_132
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch available01
What, why and how
No cwe for this issue in Visual Studio Code CoPilot Chat Extension allows an unauthorized attacker to bypass a security feature over a network.
What
No cwe for this issue in Visual Studio Code CoPilot Chat Extension allows an unauthorized attacker to bypass a security feature over a network.
Why
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
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
No cwe for this issue in Visual Studio Code CoPilot Chat Extension allows an unauthorized attacker to bypass a security feature over a network.
Why
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
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 No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.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 None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.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 → Improper Access Control → 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
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-284 ↗
CWE-284: Improper Access Control. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
- 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:U/C:N/I:H/A:L/E:U/RL:O/RC:CCommon 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.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.IHighIntegrity impact: A successful attack can cause a major loss.ALowAvailability impact: A successful attack can cause a limited loss.- 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.
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
- Action
- 1.132.1:Security Update:https://code.visualstudio.com/updates/v1_132
- 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 29 Sept 2026, 20:20 UTC · CWE-284 · Improper Access Control
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-56437
Product sourceVendor CSAF · Microsoft Security Response Center
Remediation sourceVendor CSAF · Microsoft Security Response Center
CWE sourceCISA ADP
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: msrc.microsoft.com/CVE-2026-65675; removed patch: msrc.microsoft.com/CVE-2026-65675; removed remediation: msrc.microsoft.com/CVE-2026-65675.secure@microsoft.com ↗
- Before
- patch: msrc.microsoft.com/CVE-2026-65675 · remediation: msrc.microsoft.com/CVE-2026-65675
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-65675
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- Microsoft Visual Studio Code CoPilot Chat Extension: 0.27.0 < 1.132.1 · Fixed: 1.132.1:Security Update:https://code.visualstudio.com/updates/v1_132
- After
- Microsoft Visual Studio Code CoPilot Chat Extension: 0.27.0 < 1.132.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- Remediation statusRemediation status changed from Patch available to Awaiting fix.secure@microsoft.com ↗
- Before
- Patch available
- After
- Awaiting fix
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: acn.gov.it/aggiornamenti-mensili-microsoft-23.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-23 · vendor advisory: msrc.microsoft.com/CVE-2026-65675
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-65675
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.secure@microsoft.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: acn.gov.it/aggiornamenti-mensili-microsoft-23.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-23 · vendor advisory: msrc.microsoft.com/CVE-2026-65675
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-65675
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- Microsoft Visual Studio Code CoPilot Chat Extension: 0.27.0 < 1.135 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- Microsoft Visual Studio Code CoPilot Chat Extension: 0.27.0 < 1.132.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.secure@microsoft.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Remediation statusRemediation status changed from Awaiting fix to Patch available.Microsoft Security Response Center ↗
- Before
- Awaiting fix
- After
- Patch available
- Affected versionsThe structured affected or fixed version information changed.Microsoft Security Response Center ↗
- Before
- Microsoft Visual Studio Code CoPilot Chat Extension: 0.27.0 < 1.132.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- Microsoft Visual Studio Code CoPilot Chat Extension: 0.27.0 < 1.132.1 · Fixed: 1.132.1:Security Update:https://code.visualstudio.com/updates/v1_132
- Remediation statusRemediation status changed from Mitigation available to Patch available.Microsoft Security Response Center ↗
- Before
- Mitigation available
- After
- Patch available
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: acn.gov.it/aggiornamenti-mensili-microsoft-23.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-23 · vendor advisory: msrc.microsoft.com/CVE-2026-65675
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-65675
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.secure@microsoft.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- Microsoft Visual Studio Code CoPilot Chat Extension: 0.27.0 < 2026.3.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- Microsoft Visual Studio Code CoPilot Chat Extension: 0.27.0 < 1.135 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 0.27.0 < 2026.3.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- 0.27.0 < 1.135 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 0.27.0 < 1.135 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- Microsoft Visual Studio Code CoPilot Chat Extension: 0.27.0 < 2026.3.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 0.27.0 < 1.132.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- 0.27.0 < 2026.3.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: msrc.microsoft.com/CVE-2026-65675.secure@microsoft.com ↗
- Before
- no authoritative guidance recorded
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-65675
- Remediation statusRemediation status changed from Awaiting fix to Mitigation available.CSIRT Italia ↗
- Before
- Awaiting fix
- After
- Mitigation available
CVE published
Fixed release recorded from official guidance
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.