Affects Visual Studio Code, a widely used developer tool; network bypass of security features can enable broad code/extension compromise across organizations.
CVE-2026-81378
VS Code interpretation conflict allows bypass of a security feature over the network.
Is CVE-2026-81378 being exploited?
Not confirmed. CVE-2026-81378 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-81378?
CVE-2026-81378 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-81378?
Yes. A fix has been recorded for CVE-2026-81378. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-81378 affect?
CVE-2026-81378 affects Visual Studio Code. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-81378?
Apply Microsoft update and restrict VS Code network access until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can bypass VS Code security checks to load/execute untrusted code or extensions, risking remote code execution and supply-chain compromise.
Patch when possible
- affected>= 1.0.0 and < 1.136.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.