CVE-2019-1211 | Git for Visual Studio Elevation of Privilege Vulnerability

An elevation of privilege vulnerability exists in Git for Visual Studio when it improperly parses configuration files. An attacker who successfully exploited the vulnerability could execute code in the context of another local user. To exploit the vulnerability, an authenticated attacker would need to modify Git configuration files on a system prior to a full installation of the application. The attacker would then need to convince another user on the system to execute specific Git commands. The update addresses the issue by changing the permissions required to edit configuration files.

Published: 2019-08-14 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2019-1211 is rated Moderate Risk (56.1/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.65%). Core evidence: EPSS rose +1.23% over the last day, indicating growing attacker interest. Mandatory action: Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2019-1211

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.43% 1.65% +1.23%
2 2025-12-29 0.64% 0.43% -0.22%
3 2025-03-30 0.64%

Full EPSS history (12 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-1211

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.3 3.0 HIGH
CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.3 5.9 [email protected]
3.7 2.0 LOW
AV:L/AC:H/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:H)
Exploitation requires uncommon or highly specific conditions.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
1.9 6.4 [email protected]

Weakness enumeration for CVE-2019-1211

Affected software / configurations for CVE-2019-1211

Vendor Product Version Raw CPE
microsoft visual_studio_2017 cpe:2.3:a:microsoft:visual_studio_2017:-:*:*:*:*:*:*:*
microsoft visual_studio_2017 15.9 cpe:2.3:a:microsoft:visual_studio_2017:15.9:*:*:*:*:*:*:*
microsoft visual_studio_2019 16.0 cpe:2.3:a:microsoft:visual_studio_2019:16.0:*:*:*:*:*:*:*
microsoft visual_studio_2019 16.2 cpe:2.3:a:microsoft:visual_studio_2019:16.2:*:*:*:*:*:*:*

References for CVE-2019-1211

cvelogic Threat Intelligence