How severe is CVE-2019-1414?

CVE-2019-1414 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2019-1414 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (60th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2019-1414?

CVE-2019-1414 affects Microsoft Visual Studio Code. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2019-1414?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2019-1414 published?

CVE-2019-1414 was published on 2020-01-24 and last updated on 2026-06-17.

CVE-2019-1414

CVE-2019-1414 is a high-severity vulnerability in Microsoft Visual Studio Code with a CVSS 3.x base score of 7.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 7.8)
CVSS v2: 7.2
EPSS exploit prediction: 1% (60th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Microsoft Visual Studio Code
Published: 2020-01-24
Last modified: 2026-06-17

Description

An elevation of privilege vulnerability exists in Visual Studio Code when it exposes a debug listener to users of a local computer, aka 'Visual Studio Code Elevation of Privilege Vulnerability'.

Frequently asked questions

What is CVE-2019-1414?: An elevation of privilege vulnerability exists in Visual Studio Code when it exposes a debug listener to users of a local computer, aka 'Visual Studio Code Elevation of Privilege Vulnerability'.
How severe is CVE-2019-1414?: CVE-2019-1414 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2019-1414 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (60th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-1414?: CVE-2019-1414 affects Microsoft Visual Studio Code. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2019-1414?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2019-1414 published?: CVE-2019-1414 was published on 2020-01-24 and last updated on 2026-06-17.

References

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1414

Affected products (1)

cpe:2.3:a:microsoft:visual_studio_code:*:*:*:*:*:*:*:*

More vulnerabilities in Microsoft Visual Studio Code

CVE-2026-47281 — Critical (CVSS 9.6): Improper input validation in Visual Studio Code allows an unauthorized attacker to elevate privileges over a network.
CVE-2026-41613 — High (CVSS 8.8): Session fixation in Visual Studio Code allows an unauthorized attacker to elevate privileges over a network.
CVE-2026-41109 — High (CVSS 8.8): Improper neutralization of special elements in output used by a downstream component ('injection') in GitHub Copilot…
CVE-2026-21518 — High (CVSS 8.8): Improper neutralization of special elements used in a command ('command injection') in GitHub Copilot and Visual Studio…
CVE-2025-55319 — High (CVSS 8.8): Ai command injection in Agentic AI and Visual Studio Code allows an unauthorized attacker to execute code over a…
CVE-2024-43488 — High (CVSS 8.8): Missing authentication for critical function in Visual Studio Code extension for Arduino allows an unauthenticated…

All CVEs affecting Microsoft Visual Studio Code →