Local code execution via improper name restriction
Published Jul 14, 2026 · Updated Jul 14, 2026
Code execution in Microsoft GitHub Copilot plugin for JetBrains IDEs before 1.13.0-251 allows attackers to run code via local interaction. Microsoft identifies improper restriction of file and resource names, but the affected locus and unsafe name-handling operation remain undisclosed. Exploitation requires user interaction and reaches local code execution without prior privileges, affecting confidentiality, integrity, and availability.
Summary
What happened
Code execution in Microsoft GitHub Copilot plugin for JetBrains IDEs before 1.13.0-251 allows attackers to run code via local interaction. Microsoft identifies improper restriction of file and resource names, but the affected locus and unsafe name-handling operation remain undisclosed. Exploitation requires user interaction and reaches local code execution without prior privileges, affecting confidentiality, integrity, and availability.
The record
- CVE
- CVE-2026-50510
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- Microsoft
- Product
- GitHub Copilot plugin for JetBrains IDEs
- Classifications
- CWE-641
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 2026CVE publishedPublication date reported by the CVE source.
- Jul 14, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <1.13.0-251
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
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