How severe is CVE-2016-3231?

CVE-2016-3231 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-2016-3231 being actively exploited?

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

What products are affected by CVE-2016-3231?

CVE-2016-3231 affects Microsoft Windows Diagnostics Hub. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2016-3231?

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-2016-3231 published?

CVE-2016-3231 was published on 2016-06-16 and last updated on 2026-06-17.

CVE-2016-3231

CVE-2016-3231 is a high-severity vulnerability in Microsoft Windows Diagnostics Hub 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. The underlying weakness is classified as CWE-19.

Key facts

Severity: High (CVSS 3.x base score 7.8)
CVSS v2: 7.2
EPSS exploit prediction: 2% (79th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-19
Affected product: Microsoft Windows Diagnostics Hub
Published: 2016-06-16
Last modified: 2026-06-17

Description

The Standard Collector service in Windows Diagnostics Hub mishandles library loading, which allows local users to gain privileges via a crafted application, aka "Windows Diagnostics Hub Elevation of Privilege Vulnerability."

Frequently asked questions

What is CVE-2016-3231?: The Standard Collector service in Windows Diagnostics Hub mishandles library loading, which allows local users to gain privileges via a crafted application, aka "Windows Diagnostics Hub Elevation of Privilege Vulnerability."
How severe is CVE-2016-3231?: CVE-2016-3231 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-2016-3231 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (79th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-3231?: CVE-2016-3231 affects Microsoft Windows Diagnostics Hub. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2016-3231?: 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-2016-3231 published?: CVE-2016-3231 was published on 2016-06-16 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:microsoft:windows_diagnostics_hub:-:*:*:*:*:*:*:*

Other CWE-19 vulnerabilities

CVE-2015-2373 — Critical (CVSS 10.0): The Remote Desktop Protocol (RDP) server service in Microsoft Windows 7 SP1, Windows 8, and Windows Server 2012 allows…
CVE-2014-8822 — Critical (CVSS 10.0): IOHIDFamily in Apple OS X before 10.10.2 allows attackers to execute arbitrary code in a kernel context or cause a…
CVE-2014-8817 — Critical (CVSS 10.0): coresymbolicationd in CoreSymbolication in Apple OS X before 10.10.2 does not verify that expected data types are…
CVE-2014-4488 — Critical (CVSS 10.0): IOHIDFamily in Apple iOS before 8.1.3, Apple OS X before 10.10.2, and Apple TV before 7.0.3 does not properly validate…
CVE-2014-7247 — Critical (CVSS 10.0): Unspecified vulnerability in JustSystems Ichitaro 2008 through 2011; Ichitaro Government 6, 7, 2008, 2009, and 2010;…
CVE-1999-0226 — Critical (CVSS 10.0): Windows NT TCP/IP processes fragmented IP packets improperly, causing a denial of service.

Browse all CWE-19 vulnerabilities →