How severe is CVE-2019-0808?

CVE-2019-0808 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2019-0808?

CVE-2019-0808 affects the following products: microsoft windows 7, microsoft windows server 2008.

How do I patch CVE-2019-0808?

No patch has shipped for CVE-2019-0808 yet — track the microsoft windows 7 advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2019-0808 across my infrastructure?

Inventory every microsoft windows 7 deployment and check each version against the affected-products list above.

How do I mitigate CVE-2019-0808 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Is CVE-2019-0808 actively exploited in the wild?

Yes. There are 13 known exploit references for CVE-2019-0808, including 1 documented proof-of-concept exploit on Exploit-DB and 9 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-0808?

CVE-2019-0808 has an EPSS (Exploit Prediction Scoring System) score of 53.0%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2019-0808 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2019-0808 (Microsoft Win32k Privilege Escalation Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-05-03. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

Which products and versions are affected by CVE-2019-0808?

CVE-2019-0808 affects microsoft windows 7; microsoft windows server 2008 (1 version, e.g. r2). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2019-0808 published, and has it been updated?

CVE-2019-0808 was published on April 9, 2019 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

HIGH severity

CVE-2019-0808 — Windows 7

HIGH

CVE-2019-0808 is a high-severity (CVSS 7.8) vulnerability in microsoft windows 7. It is in CISA's Known Exploited Vulnerabilities catalog (added 2021-11-03) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in memory, aka 'Win32k Elevation of Privilege Vulnerability'. This…

Published

Apr 9, 2019

Updated

Jun 17, 2026

Affected

2 products

Patched

See advisory

Exploits

13 known

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2021-11-03. Federal agencies were required to remediate by 2022-05-03.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2019-0808.

EPSS Exploitation Probability

via FIRST.org ↗

53.0%probability of exploitation in next 30 days

High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2019-0808 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Counts from FIRST.org, log-scaled.

Description

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in memory, aka 'Win32k Elevation of Privilege Vulnerability'. This CVE ID is unique from CVE-2019-0797.

Affected Products

2 products · 3 configurations

windows 7microsoft

all

windows server 2008microsoft

1 version

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-46604doswindows

Microsoft Windows 7/2008 - 'Win32k' Denial of Service (PoC)

by ze0r · Mar 26, 2019

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every microsoft windows 7 deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2019-0808 yet — track the microsoft windows 7 advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2019-0808 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

Protect my workloads How runtime protection works