CVE-2026-81383
HIGHCVSS 7.4/10EPSS 0.71%
Last modified
CVE-2026-81383 is a high-severity vulnerability rated 7.4/10 on the CVSS scale. Use of incorrectly-resolved name or reference in Visual Studio Code allows an unauthorized attacker to disclose information over a network.. EPSS estimates a 0.71% chance of exploitation in the next 30 days.
Description
Use of incorrectly-resolved name or reference in Visual Studio Code allows an unauthorized attacker to disclose information over a network.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Microsoft | Visual Studio Code | < 1.136.2 |
References
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-81383Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-81383?
Use of incorrectly-resolved name or reference in Visual Studio Code allows an unauthorized attacker to disclose information over a network.
How severe is CVE-2026-81383?
CVE-2026-81383 has a CVSS score of 7.4/10 (HIGH severity). The EPSS model estimates a 0.71% probability of exploitation in the next 30 days.
How do I fix CVE-2026-81383?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-81377Improper limitation of a pathname to a restricted directory …6.5
- CVE-2026-81378Interpretation conflict in Visual Studio Code allows an unau…8.2
- CVE-2026-81379Not failing securely ('failing open') in Visual Studio Code …8.2
- CVE-2026-8138A vulnerability was found in Tenda CX12L 16.03.53.12. This i…8.8
- CVE-2026-81380Improper neutralization of special elements used in a comman…5.3
- CVE-2026-81381Insufficiently protected credentials in GitHub Copilot and V…7.5
- CVE-2026-81385Deserialization of untrusted data in Microsoft Office Publis…8.8
- CVE-2026-81386Heap-based buffer overflow in Microsoft Office Excel allows …7.8
- CVE-2026-81387Exposure of sensitive system information to an unauthorized …5.5
- CVE-2026-81388Stack-based buffer overflow in Microsoft Office Excel allows…7.8
- CVE-2026-81389Heap-based buffer overflow in Microsoft Office Excel allows …7
- CVE-2026-8139Concrete CMS 9.5.0 and below is vulnerable to Stored XSS via…5.4
Are you affected by CVE-2026-81383?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST