CVE-2020-0981
A security feature bypass vulnerability exists when Windows fails to properly handle token...
A security feature bypass vulnerability exists when Windows fails to properly handle token relationships.An attacker who successfully exploited the vulnerability could allow an application with a certain integrity level to execute code at a different integrity level, leading to a sandbox escape.The update addresses the vulnerability by correcting how Windows handles token relationships, aka 'Windows Token Security Feature Bypass Vulnerability'.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
A security feature bypass vulnerability exists when Windows fails to properly handle token relationships.An attacker who successfully exploited the vulnerability could allow an application with a certain integrity level to execute code at a different integrity level, leading to a sandbox escape.The update addresses the vulnerability by correcting how Windows handles token relationships, aka 'Windows Token Security Feature Bypass Vulnerability'.
- Record
CVE-2020-0981- CVSS 3.1
- 8.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - CVSS 2.0
- 4.6 Medium
AV:L/AC:L/Au:N/C:P/I:P/A:P - Weakness
- CWE-863
- Updated
- 2026-11-02
CVE List No score
A security feature bypass vulnerability exists when Windows fails to properly handle token relationships.An attacker who successfully exploited the vulnerability could allow an application with a certain integrity level to execute code at a different integrity level, leading to a sandbox escape.The update addresses the vulnerability by correcting how Windows handles token relationships, aka 'Windows Token Security Feature Bypass Vulnerability'.
- Record
CVE-2020-0981- Updated
- 2026-11-02
EUVDEUVD-2020-2447 No score
A security feature bypass vulnerability exists when Windows fails to properly handle token relationships.An attacker who successfully exploited the vulnerability could allow an application with a certain integrity level to execute code at a different integrity level, leading to a sandbox escape.The update addresses the vulnerability by correcting how Windows handles token relationships, aka 'Windows Token Security Feature Bypass Vulnerability'.
- Record
EUVD-2020-2447- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-93vj-6w32-x9gc No score
A security feature bypass vulnerability exists when Windows fails to properly handle token...
A security feature bypass vulnerability exists when Windows fails to properly handle token relationships.An attacker who successfully exploited the vulnerability could allow an application with a certain integrity level to execute code at a different integrity level, leading to a sandbox escape.The update addresses the vulnerability by correcting how Windows handles token relationships, aka 'Windows Token Security Feature Bypass Vulnerability'.
- Record
GHSA-93vj-6w32-x9gc- Weakness
- CWE-74
- Updated
- 2026-11-02
Affected products
- microsoft windows 10 version 1903 for 32-bit systems
- microsoft windows 10 version 1903 for arm64-based systems
- microsoft windows 10 version 1903 for x64-based systems
- microsoft windows 10 version 1909 for 32-bit systems
- microsoft windows 10 version 1909 for arm64-based systems
- microsoft windows 10 version 1909 for x64-based systems
- microsoft windows server, version 1903 (server core installation)
- microsoft windows server, version 1909 (server core installation)
- microsoft windows 10
- microsoft windows server 2016
History
| Recorded | Changed | Sources |
|---|---|---|
| facts | ||
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2020-0981 is a high vulnerability (CVSS 8.8) in Microsoft Windows 10 Version 1903 For 32-bit Systems, published April 15, 2020. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.27%, the 70th percentile. No source names a fixed version.