How severe is CVE-2019-1077?

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

Is CVE-2019-1077 being actively exploited?

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

What products are affected by CVE-2019-1077?

CVE-2019-1077 primarily affects Microsoft Visual Studio 2017. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2019-1077?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2019-1077 published?

CVE-2019-1077 was published on 2019-07-15 and last updated on 2026-06-17.

CVE-2019-1077

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

Key facts

Severity: Medium (CVSS 3.x base score 5.0)
CVSS v2: 6.6
EPSS exploit prediction: 2% (75th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Microsoft Visual Studio 2017
Published: 2019-07-15
Last modified: 2026-06-17

Description

An elevation of privilege vulnerability exists when the Visual Studio updater service improperly handles file permissions, aka 'Visual Studio Elevation of Privilege Vulnerability'.

Frequently asked questions

What is CVE-2019-1077?: An elevation of privilege vulnerability exists when the Visual Studio updater service improperly handles file permissions, aka 'Visual Studio Elevation of Privilege Vulnerability'.
How severe is CVE-2019-1077?: CVE-2019-1077 has a CVSS 3.x base score of 5.0, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2019-1077 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (75th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-1077?: CVE-2019-1077 primarily affects Microsoft Visual Studio 2017. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2019-1077?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2019-1077 published?: CVE-2019-1077 was published on 2019-07-15 and last updated on 2026-06-17.

References

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

Affected products (3)

cpe:2.3:a:microsoft:visual_studio_2017:15.9:*:*:*:*:*:*:*
cpe:2.3:a:microsoft:visual_studio_2019:16.0:*:*:*:*:*:*:*
cpe:2.3:a:microsoft:visual_studio_2019:16.1:*:*:*:*:*:*:*

More vulnerabilities in Microsoft Visual Studio 2017

CVE-2025-49739 — High (CVSS 8.8): Improper link resolution before file access ('link following') in Visual Studio allows an unauthorized attacker to…
CVE-2025-21178 — High (CVSS 8.8): Visual Studio Remote Code Execution Vulnerability
CVE-2025-21176 — High (CVSS 8.8): .NET, .NET Framework, and Visual Studio Remote Code Execution Vulnerability
CVE-2022-35827 — High (CVSS 8.8): Visual Studio Remote Code Execution Vulnerability
CVE-2022-35826 — High (CVSS 8.8): Visual Studio Remote Code Execution Vulnerability
CVE-2022-35825 — High (CVSS 8.8): Visual Studio Remote Code Execution Vulnerability

All CVEs affecting Microsoft Visual Studio 2017 →