CVE-2016-3393 [Exploited] | Microsoft WINDOWS 10 1507 RCE

CVE-2016-3393 is rated Critical Active Threat (95.5/100): CVSS High severity, with high exploitation likelihood (EPSS 55.74%, 98th percentile). CISA KEV confirms active exploitation (added 2022-05-25) affecting Microsoft / Windows. Unauthenticated remote administrative access may be possible. EPSS rose +5.37% over the last day, indicating growing attacker interest. The CISA remediation deadline has passed—treat as an emergency patch priority.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-05-02	50.37%	55.74%	+5.37%
2	2026-04-23	53.09%	50.37%	-2.72%
3	2026-04-01	—	53.09%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-05-02

50.37%

55.74%

+5.37%

2026-04-23

53.09%

50.37%

-2.72%

2026-04-01

—

53.09%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:N/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: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.	1.8	5.9	[email protected]
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:N/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: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.	1.8	5.9	134c704f-9b21-4f2e-91b3-4a467353bcc0
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

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:N/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: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.

1.8

5.9

[email protected]

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:N/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: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.

1.8

5.9

134c704f-9b21-4f2e-91b3-4a467353bcc0

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]

Affected software / configurations for CVE-2016-3393

Vendor	Product	Version	Raw CPE
microsoft	windows_10_1507	—	cpe:2.3:o:microsoft:windows_10_1507:-:::::::*
microsoft	windows_10_1511	—	cpe:2.3:o:microsoft:windows_10_1511:-:::::::*
microsoft	windows_10_1607	—	cpe:2.3:o:microsoft:windows_10_1607:-:::::::*
microsoft	windows_7	—	cpe:2.3:o:microsoft:windows_7:-:sp1::::::
microsoft	windows_8.1	—	cpe:2.3:o:microsoft:windows_8.1:-:::::::*
microsoft	windows_rt_8.1	—	cpe:2.3:o:microsoft:windows_rt_8.1:-:::::::*
microsoft	windows_server_2008	—	cpe:2.3:o:microsoft:windows_server_2008:-:sp2::::::
microsoft	windows_server_2008	r2	cpe:2.3:o:microsoft:windows_server_2008:r2:sp1::::::
microsoft	windows_server_2012	—	cpe:2.3:o:microsoft:windows_server_2012:-:::::::*
microsoft	windows_server_2012	r2	cpe:2.3:o:microsoft:windows_server_2012:r2:::::::*
microsoft	windows_vista	—	cpe:2.3:o:microsoft:windows_vista:-:sp2::::::

References for CVE-2016-3393

URL	Tags
http://www.securityfocus.com/bid/93377	Broken Link Third Party Advisory VDB Entry
http://www.securitytracker.com/id/1036988	Broken Link Third Party Advisory VDB Entry
https://docs.microsoft.com/en-us/security-updates/securitybulletins/2016/ms16-120	Patch Vendor Advisory
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2016-3393	US Government Resource

URL

CVE-2016-3393

CISA KEV Record for CVE-2016-3393

Exploit prediction scoring system (EPSS) score for CVE-2016-3393

Common vulnerability scoring system (CVSS) metrics for CVE-2016-3393

Weakness enumeration for CVE-2016-3393

Affected software / configurations for CVE-2016-3393

References for CVE-2016-3393