Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.62% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-81380High confidence
GitHub Copilot and Visual Studio Code Information Disclosure Vulnerability
Microsoft · Visual Studio Code
5.3MediumCVSS 3.1
Scheduled
Patch availableMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Medium, 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 Visual Studio Code 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.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Patch available01
What, why and how
Improper neutralization of special elements used in a command ('command injection') in GitHub Copilot and Visual Studio Code allows an unauthorized attacker to disclose information over a network.
What
Improper neutralization of special elements used in a command ('command injection') in GitHub Copilot and Visual Studio Code allows an unauthorized attacker to disclose information over a network.
Why
Untrusted input reaches a command interpreter without sufficient validation or separation from command syntax.
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
Improper neutralization of special elements used in a command ('command injection') in GitHub Copilot and Visual Studio Code allows an unauthorized attacker to disclose information over a network.
Why
Untrusted input reaches a command interpreter without sufficient validation or separation from command syntax.
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 Neutralization of Special Elements used in a Command ('Command Injection') → 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
- High: exploitation depends on specific conditions
- 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-77 ↗
CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection'). The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
- 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:H/PR:N/UI:R/S:U/C:H/I:N/A:N/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.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.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.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.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.
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
- 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 8 Sept 2026 · Last source change 1 Oct 2026, 22:56 UTC · CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-09-09
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-73336
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
View recent updates ↗What changed after publication
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24 · vendor advisory: msrc.microsoft.com/CVE-2026-81380
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-81380
- 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-24.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24 · vendor advisory: msrc.microsoft.com/CVE-2026-81380
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-81380
- 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-24.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24 · vendor advisory: msrc.microsoft.com/CVE-2026-81380
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-81380
- 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-24.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24 · vendor advisory: msrc.microsoft.com/CVE-2026-81380
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-81380
- 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-24.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24 · vendor advisory: msrc.microsoft.com/CVE-2026-81380
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-81380
- 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-24.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24 · vendor advisory: msrc.microsoft.com/CVE-2026-81380
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-81380
- 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-24.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24 · vendor advisory: msrc.microsoft.com/CVE-2026-81380
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-81380
- 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-24.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24 · vendor advisory: msrc.microsoft.com/CVE-2026-81380
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-81380
- 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-24.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24 · vendor advisory: msrc.microsoft.com/CVE-2026-81380
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-81380
- 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-24.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24 · vendor advisory: msrc.microsoft.com/CVE-2026-81380
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-81380
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.secure@microsoft.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: msrc.microsoft.com/CVE-2026-81380.secure@microsoft.com ↗
- Before
- no authoritative guidance recorded
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-81380
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24.CNA ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24
- After
- no authoritative guidance recorded
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.CNA ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24.CNA ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-24
- After
- no authoritative guidance recorded
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.CNA ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 1.0.0 < 1.136.2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- Visual Studio Code: 1.0.0 < 1.136.2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- ENISA EUVD mappingEUVD-2026-73336 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2026-73336"}
- Remediation statusRemediation status changed from Awaiting fix to Mitigation available.CSIRT Italia ↗
- Before
- Awaiting fix
- After
- Mitigation available
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
CVE published
Remediation guidance recorded
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.