CVE-2019-1349 [High] | Input Validation Bypass in Visual Studio 2017

CVE-2019-1349 is rated High Risk (74.6/100): CVSS High severity, with high exploitation likelihood (EPSS 34.01%, 98th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. EPSS rose +14.32% over the last day, indicating growing attacker interest. High exploitation likelihood—assess exposure and prioritize remediation.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	19.69%	34.01%	+14.32%
2	2026-05-26	28.41%	19.69%	-8.72%
3	2026-02-24	—	28.41%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

19.69%

34.01%

+14.32%

2026-05-26

28.41%

19.69%

-8.72%

2026-02-24

—

28.41%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.8	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. 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:N) No account or special rights needed—anonymous or random user is enough. 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.	2.8	5.9	[email protected]
9.3	2.0	HIGH	`AV:N/AC:M/Au:N/C:C/I:C/A:C` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:M) Exploitation needs some favorable conditions, but not exceptional ones. Authentication (AU:N) No authentication is required. Confidentiality impact (C:C) Complete confidentiality impact. Integrity impact (I:C) Complete integrity impact. Availability impact (A:C) Complete availability impact.	8.6	10.0	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.8

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
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:N): No account or special rights needed—anonymous or random user is enough.
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.

2.8

5.9

[email protected]

9.3

2.0

HIGH

AV:N/AC:M/Au:N/C:C/I:C/A:C Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:M): Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:C): Complete confidentiality impact.
Integrity impact (I:C): Complete integrity impact.
Availability impact (A:C): Complete availability impact.

8.6

10.0

[email protected]

OS Trackers for CVE-2019-1349

vendor	priority	summary	link
`alpine`	high	CVE-2019-1349: 5 source package rows (git, libgit2, libgit2-1.0, libgit2-1.1, libgit2-1.5); 21 state rows across 17 repos (3.10-main, 3.11-main, 3.12-main, 3.17-community, 3.17-main, 3.18-community, 3.18-main, 3.19-community, 3.19-main, 3.20-community, 3.20-main, 3.21-community, 3.21-main, 3.22-community, 3.22-main, edge-community, edge-main); fixed 21, open 0.	https://security.alpinelinux.org/vuln/CVE-2019-1349
`debian`	not yet assigned	CVE-2019-1349 not yet assigned priority: Debian including 1 source packages (git), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2019-1349
`gentoo`	normal	CVE-2019-1349: 1 GLSA(s) (202003-30), 1 atom(s) (dev-vcs/git); latest impact normal.	https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2019-1349
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2019-1349
`ubuntu`	low	CVE-2019-1349 low priority: Ubuntu including 1 source packages (git), 6 status rows across 6 suites (bionic, disco, eoan, trusty, upstream, xenial): released 5, DNE 1.	https://ubuntu.com/security/CVE-2019-1349

Affected software / configurations for CVE-2019-1349

Vendor	Product	Version	Raw CPE
microsoft	visual_studio_2017	>= 15.0, < 15.9.18	cpe:2.3:a:microsoft:visual_studio_2017::::::::
microsoft	visual_studio_2019	>= 16.0, < 16.4.1	cpe:2.3:a:microsoft:visual_studio_2019::::::::

References for CVE-2019-1349

URL	Tags
http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00056.html
http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00003.html
https://access.redhat.com/errata/RHSA-2020:0228
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1349	Patch Vendor Advisory
https://public-inbox.org/git/xmqqr21cqcn9.fsf%40gitster-ct.c.googlers.com/
https://security.gentoo.org/glsa/202003-30

URL

CVE-2019-1349

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

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

Weakness enumeration for CVE-2019-1349

OS Trackers for CVE-2019-1349

Affected software / configurations for CVE-2019-1349

References for CVE-2019-1349